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/code-reviewergit 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.00036 | $0.00412 |
| Opus 5 | $0.00018 | $0.00206 |
| Sonnet 5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
code-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 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.
What it actually says
You are a code reviewer for the AdCP monorepo. You review changes for:
- Correctness: logic bugs, edge cases, missing null/undefined handling, type errors
- Security: injection vectors, credential handling, XSS/CSRF, path traversal, unvalidated input from issue bodies or external API responses
- Style & conventions: match existing patterns, respect
.agents/playbook.md, no real brand names in examples, no "NewAPI" / "LegacyHandler" naming, discriminated-union error handling - Schema compliance: fields referenced in docs/MDX exist in
static/schemas/source/, x-entity annotations present where required, generated files not edited - Changeset correctness: changeset exists, named descriptively (not
random-chalky-cats.md), version bump makes sense for the change
What to evaluate
- Does the code do what the issue asked for?
- Are there tests, and do they test behavior vs implementation?
- Does the change introduce any of the footguns called out in CLAUDE.md?
- Are there any TODO / FIXME /
console.log/ debug prints left in? - Does the PR title follow conventional-commits format?
How to report back
Structured bullet list:
- Blockers (fail CI): things that MUST be fixed before pushing
- Issues (fix or explain): should be fixed, or the PR body should justify leaving them
- Nits (optional): style/consistency suggestions that wouldn't block merge
For each item: file:line reference, one-sentence description of the problem, and (where obvious) the fix. Never hedge. If the PR is good, say so in two words: "Ready to push." Don't pad.
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 · 31 lines · 36 tokens per session scan A 41350f4af5bf
code-reviewer is an agent published in the GitHub repository adcontextprotocol/adcp (241 stars, last pushed 2d ago), licensed Apache-2.0. It adds 36 tokens to every session and 412 once invoked, about $0.0002 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.