RedAmon is an AI framework that connects reconnaissance, exploitation, and post-exploitation activities into an automated security-testing pipeline, while organizing findings and proposing code fixes. It is for authorized penetration testing, security research, and education. The catalogue entries provide skills and instructions for working with the framework.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/samugit83/redamon/llm-provider-integrationnpx skills add samugit83/redamon --skill llm-provider-integrationgit clone --depth 1 https://github.com/samugit83/redamonWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/samugit83/redamon/llm-provider-integration)<a href="https://agentmods.dev/skills/samugit83/redamon/llm-provider-integration"><img src="https://agentmods.dev/badge/skills/samugit83/redamon/llm-provider-integration.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00109 | $0.00709 |
| Opus 5 | $0.00055 | $0.00354 |
| Sonnet 5 | $0.00022 | $0.00142 |
| Haiku 4.5 | $0.00011 | $0.00071 |
Grade A, and why
llm-provider-integration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
- NEVER let a provider API key reach a scan container. Keys live in exactly
two places: Postgres
user_llm_providersrows and, in transit, on the wire between webapp and agent. The recon / scan / MCP containers must never see them. Do not thread a provider key through recon settings or container env. - NEVER add a model id that is not prefix-routed. Anything other than
claude-*and bare OpenAI ids MUST carry aprovider/<model>prefix, resolved byparse_model_provider()at agentic/orchestrator_helpers/llm_setup.py:67. An unprefixed id routes to the wrong provider silently. - ALWAYS register the provider in the webapp provider-type registry and propagate the key kwarg into every LLM call site. A provider registered but not propagated builds a client with no credentials. The guide enumerates all 11 integration points; touch each.
The two invariants
| Invariant | Where | Failure if broken |
|---|---|---|
| Keys only in Postgres + webapp<->agent transit | webapp/prisma/schema.prisma user_llm_providers; agent settings fetch |
key leaks into scan/MCP containers |
| Model id prefix routing | parse_model_provider() llm_setup.py:67 |
model routes to the wrong provider |
Commands
docker compose build agent && docker compose up -d agent # agentic/ is baked
docker compose exec webapp npx prisma db push # provider schema changes (NEVER prisma migrate)
Resources
- docs/readmes/coding_agent_prompts/PROVIDER_INTEGRATION_GUIDELINES.md - the 11 integration points, decision tree, and model-id prefix table
- Related skill:
agentic-tool-integration
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 64 lines · 109 tokens per session scan A d8bd31bde654
llm-provider-integration is a skill published in the GitHub repository samugit83/redamon (2,391 stars, last pushed 2d ago), licensed MIT. It adds 109 tokens to every session and 709 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
custom-data-tool
Custom tool for data processing.
azure-openai-to-responses
Migrate Python apps from Azure OpenAI Chat Completions to the Responses API. Covers AzureOpenAI/AsyncAzureOpenAI client migration to the v1 endpoint, streaming, tools, structured output, multi-turn, EntraID auth, and model compatibility checks. Python-focused, Azure OpenAI-specific. USE FOR: migrate to responses API…
agent-v3-memory-specialist
Agent skill for v3-memory-specialist - invoke with $agent-v3-memory-specialist.
agent-neural-network
Agent skill for neural-network - invoke with $agent-neural-network.
embeddings
Vector embeddings with HNSW indexing, sql.js persistence, and hyperbolic support. 75x faster with agentic-flow integration. Use when: semantic search, pattern matching, similarity queries, knowledge retrieval. Skip when: exact text matching, simple lookups, no semantic understanding needed.
neural-training
Neural pattern training with SONA (Self-Optimizing Neural Architecture), MoE (Mixture of Experts), and EWC++ for knowledge consolidation. Use when: pattern learning, model optimization, knowledge transfer, adaptive routing. Skip when: simple tasks, no learning required, one-off operations.