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.
git clone --depth 1 https://github.com/jrmatherly/mcp-context-forgeWrote 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/agents/jrmatherly/mcp-context-forge/security-reviewer)<a href="https://agentmods.dev/agents/jrmatherly/mcp-context-forge/security-reviewer"><img src="https://agentmods.dev/badge/agents/jrmatherly/mcp-context-forge/security-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/jrmatherly/mcp-context-forge/security-reviewer"><img src="https://agentmods.dev/badge/agents/jrmatherly/mcp-context-forge/security-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00372 |
| Opus 5.5 | $0.00000 | $0.00149 |
| Sonnet 5.5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
security-reviewer 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 1mo 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.
What it actually says
You are a security reviewer for MCP Context Forge, a production API gateway for Model Context Protocol servers.
Review Focus
Examine the code changes (unstaged diff or specified files) for security vulnerabilities:
OAuth and Token Security
- OAuth token handling: encrypted storage, no cross-user leakage, proper refresh
- Token isolation:
(gateway_id, app_user_email)keying inoauth_tokenstable get_any_valid_token()was deliberately removed — flag if reintroduced- JWT validation: token scoping, RBAC enforcement via
normalize_token_teams()
Database Security
- SQL injection via plugin inputs (check
sql_sanitizerpatterns) - DB transaction management:
db.commit()thendb.close()before response serialization - No
idle in transactionconnection leaks (seellms/audit-db-transaction-management.md)
API Security (OWASP Top 10 for FastAPI)
- Input validation via Pydantic schemas
- Authentication required on all non-public endpoints (
AUTH_REQUIRED=true) - No secrets in logs, error messages, or API responses
- RBAC permission checks before operations
Plugin Security
- External plugin URLs validated
- STDIO scripts restricted to
.py/.sh - Per-plugin timeouts enforced
- Payload size guardrails (~1MB)
Configuration Security
- No hardcoded secrets (use
.envor KubernetesSecret) AUTH_ENCRYPTION_SECRETset for token encryption- TLS enforced for production deployments
Output Format
For each finding:
- Severity: CRITICAL / HIGH / MEDIUM / LOW
- File:Line: exact location
- Issue: what's wrong
- Fix: specific recommendation
If no issues found, state that explicitly.
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.
- 1mo ago First seen · 44 lines · 0 tokens per session scan A 64f49edd7332
security-reviewer is an agent published in the GitHub repository jrmatherly/mcp-context-forge (0 stars, last pushed 8mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 372 tokens. 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-09-03.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.