# LLM Provider Integration

Adding an LLM provider to RedAmon: the credential boundary (keys must never reach scan...

- Repository: https://github.com/samugit83/redamon (3261 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add samugit83/redamon --skill llm-provider-integration -g -a claude-code -y`
Codex: `npx skills add samugit83/redamon --skill llm-provider-integration -g -a codex -y`
Cursor: `npx skills add samugit83/redamon --skill llm-provider-integration -g -a cursor -y`
Gemini CLI: `npx skills add samugit83/redamon --skill llm-provider-integration -g -a gemini-cli -y`

## Description

Adding an LLM provider to RedAmon: the credential boundary (keys must never reach scan containers), prefix-routed model ids, and the provider registry. A misrouted model id or a leaked key are the two failures this guards. Trigger: adding or editing an LLM provider; editing parse_model_provider in agentic/orchestrator_helpers/llm_setup.py, the webapp provider-type registry, the user_llm_providers model, or an LLM call site that passes an API key; a non-chat provider type (TypeSafe Jev) or a path that picks "any provider row".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## When to Use

- Adding a new LLM provider (OpenAI-compatible or otherwise) the agent can use.

For a non-LLM external API *tool*, use `agentic-tool-integration`.

---

## Critical Rules

The rest: https://github.com/samugit83/redamon/blob/HEAD/skills/llm-provider-integration/SKILL.md