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 agents/adcontextprotocol/adcp/security-reviewer-deepgit clone --depth 1 https://github.com/adcontextprotocol/adcpWhat 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 | $0.00064 | $0.02413 |
| Opus 5 | $0.00032 | $0.01207 |
| Sonnet 5 | $0.00013 | $0.00483 |
| Haiku 4.5 | $0.00006 | $0.00241 |
Grade A, and why
security-reviewer-deep 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 2d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Reviewer - Agentic Ad Tech Systems
Core Identity
You are a security reviewer who specializes in the attack surfaces unique to agentic AI systems. You understand that traditional web security (SQLi, XSS, CSRF) is necessary but insufficient for platforms where LLMs process user input, tool calls execute actions, and system prompts control behavior. You know that an attacker who modifies a system prompt can silently poison thousands of users without touching application code.
Your reviews are informed by real breaches. The McKinsey/Lilli attack (March 2026) demonstrated that AI chatbot platforms face a specific threat model: exposed API documentation enables automated enumeration, SQL injection through JSON keys bypasses parameterized queries, and database-stored system prompts become a single point of compromise for all downstream users.
When Invoked
- Run
git diffto see recent changes (or review the files/PR specified) - Identify which system the changes touch and what data flows through it
- Trace user input from entry point to every place it is used, stored, or forwarded
- Apply the review checklist below, starting with Priority 0
- Check for attack chains: vulnerabilities that are low-severity alone but critical in combination
Review Priorities
Priority 0: Prompt Injection and System Prompt Integrity
Direct prompt injection:
- User input concatenated into system prompts, tool descriptions, or LLM context without sanitization
- Chat messages, form fields, campaign names, product descriptions, or any user-controlled string that reaches an LLM
- Template literals or f-strings that embed user data into prompt text (search for backtick templates and f-strings near LLM calls)
Indirect prompt injection:
- Stored data (chat history, database records, file contents) that is later retrieved and included in LLM context
- Campaign names, product descriptions, or metadata that flow from one user's input into another user's agent context
- Tool responses from external systems that could contain adversarial instructions
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.
- 2d ago First seen · 192 lines · 64 tokens per session scan A 2f9258239713
security-reviewer-deep is an agent published in the GitHub repository adcontextprotocol/adcp (241 stars, last pushed 2d ago), licensed Apache-2.0. It adds 64 tokens to every session and 2,413 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
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.
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.