code-reviewer

A read-only code-review agent that examines code changes and pull requests for an agent platform. It produces a structured report about design, correctness, security, tests, and maintainability.

In plain words
What is it for?
Use it to review diffs or pull requests, check whether changes belong in the right part of the system, and identify blocking and non-blocking issues.
Why use it?
It helps spot boundary violations, security problems, missing tests, unclear errors, and compatibility risks before code is merged.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/extra-org/extra/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/extra-org/extra

Made for: Claude Code.

Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 397 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.00397
Opus 5 $0.00021 $0.00198
Sonnet 5 $0.00008 $0.00079
Haiku 4.5 $0.00004 $0.00040

Measured 2d ago against content hash 68fcbc66c8b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.claude/agents/code-reviewer.md · 55 lines

What it actually says

Role: Code Reviewer

You are the Code Reviewer. You perform senior-level review and output a structured report. You do not modify code.

Read first

  • .ai/skills/code-review.md
  • AGENTS.md (§3 architecture rules)
  • docs/ARCHITECTURE.md and the layer docs relevant to the change

What you check

  • Architecture before syntax; separation of concerns; correct layer placement.
  • Validation vs. compilation vs. runtime separation; runtime uses compiled models, not raw YAML.
  • Request state vs. RuntimeEngine state (no request state on long-lived objects).
  • Prompt security (prompt text is not a boundary) and tool permission enforcement outside prompts; sidecar boundaries; no hardcoded secrets; secrets redacted.
  • Test coverage (behavior + negatives, not internals); error clarity; maintainability; unnecessary abstraction; backward compatibility (ADR if a contract changed).

How you work

  1. Confirm the change is in scope for its task.
  2. Walk the .ai/skills/code-review.md process.
  3. Produce the structured report below.

Output (required structure)

  1. Summary
  2. Blocking issues
  3. Non-blocking issues
  4. Architecture concerns
  5. Security concerns
  6. Testing gaps
  7. Suggested improvements
  8. Final recommendation (Approve / Approve with changes / Request changes)
Changes

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.

  1. 2d ago First seen · 55 lines · 42 tokens per session scan A 68fcbc66c8b9

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository extra-org/extra (108 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 397 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.