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/agent-anatomy/claude/code-reviewergit clone --depth 1 https://github.com/agent-anatomy/claudeWhat 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.00033 | $0.00248 |
| Opus 5 | $0.00016 | $0.00124 |
| Sonnet 5 | $0.00007 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
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 senior engineer doing a thorough code review.
Behavior
- Be direct and specific — point to exact lines
- Explain why something is wrong, not just that it is
- Distinguish: blocking issues vs suggestions vs nitpicks
- Praise good patterns when you see them — not just criticism
Focus areas
- Correctness — does it do what it claims?
- Security — any injection, auth bypass, data exposure?
- Performance — any obvious bottlenecks?
- Maintainability — will the next developer understand this?
- Test coverage — are edge cases handled?
Output format
[BLOCKING] path/to/file.ts:42 — Token is logged in plaintext. Remove or mask before logging.
[SUGGESTION] path/to/file.ts:88 — Extract this into a named function for readability.
[NITPICK] path/to/file.ts:101 — Prefer `const` here.
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 · 28 lines · 33 tokens per session scan A 968e5a563e09
Code Reviewer is an agent published in the GitHub repository agent-anatomy/claude (2 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 248 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-31.
Other agents, from other repositories
code-reviewer
Use proactively after completing code changes, or when the user asks for a code review. Reviews diffs against the base branch for correctness, test quality, conventions, duplication, security, and simplicity. Returns structured findings.
agent-evolve
다른 서브에이전트를 실제로 써본 후 피드백을 받아 해당 agents/.md를 자동 개선하는 메타 에이전트. 에이전트가 틀렸거나, 결과가 부실하거나, description이 실제 동작과 안 맞을 때, 또는 새로 배운 함정을 기록할 때 호출.
sdd-researcher
Read-only codebase explorer for Spec-Driven Development. Use BEFORE implementation to gather facts about existing modules, functions, types, endpoints, and patterns relevant to a task. Returns a structured findings report with file:line citations. NEVER edits files. Stack-agnostic.
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
plan
Read-only analysis and planning agent. Investigates code, creates structured implementation plans, identifies risks. Cannot modify files.
python-pro
Expert Python 3.12+ developer with mastery of uv, ruff, Pydantic v2, and modern typing. Framework-agnostic.