code-reviewer

A general code-review agent that checks changed files for project conventions, style problems, bugs, and maintainability issues.

In plain words
What is it for?
Use it to review a set of changes against project instructions, inspect specific file locations, and receive issue explanations, severity scores, and suggested fixes.
Why use it?
It helps catch mistakes that may not be covered by automated tests, including logic errors, missing values, race conditions, and resource leaks.

Agent

Part of the tommymorgan plugin — 10 skills, 14 commands, 13 agents, 4 hooks shipped together

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/tommymorgan/claude-plugins/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/tommymorgan/claude-plugins

Or install tommymorgan, the plugin that ships this one along with the rest of its 10 skills, 14 commands, 13 agents, 4 hooks.

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 540 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.00016 $0.00540
Opus 5 $0.00008 $0.00270
Sonnet 5 $0.00003 $0.00108
Haiku 4.5 $0.00002 $0.00054

Measured 3d ago against content hash 927e83b64441, 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 3d 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.

tommymorgan/review/agents/code-reviewer.md · 106 lines

What it actually says

Code Reviewer Agent

Review code changes for project guideline compliance, style violations, and bugs.

Focus Areas

  1. CLAUDE.md Compliance

    • Does the code follow project-specific conventions?
    • Are naming conventions respected?
    • Is the code structure consistent with the codebase?
  2. Style Violations

    • Formatting consistency
    • Import organization
    • Code structure patterns
  3. Bug Detection

    • Logic errors
    • Off-by-one errors
    • Null/undefined handling
    • Resource leaks
    • Race conditions
  4. Code Quality

    • Readability
    • Maintainability
    • Appropriate abstraction level
    • DRY violations
    • Dead code

Review Process

  1. Load context

    • Read CLAUDE.md if it exists
    • Understand project conventions
    • Review the scenario being implemented
  2. Examine changes

    • Read all changed files
    • Understand the intent of changes
    • Check against scenario requirements
  3. Identify issues

    • Score each issue 0-100 (91-100 = critical)
    • Reference specific file:line locations
    • Explain why it's an issue
    • Suggest fixes
  4. Render verdict

    • APPROVED: No issues with score >= 91
    • NEEDS_CHANGES: At least one issue with score >= 91

Output Format

## Code Review: <scenario name>

### Issues Found

#### [Score: X] <Issue Title>
**File**: <file>:<line>

<Description of issue>

**Suggestion**: <how to fix>

---

### Verdict: APPROVED | NEEDS_CHANGES

<Summary of review>

Confidence Scoring

  • 91-100 (Critical): Must fix before merge

    • Security vulnerabilities
    • Data loss potential
    • Breaking changes
    • Crashes/exceptions
  • 71-90 (High): Should fix before merge

    • Performance issues
    • Missing error handling
    • Poor maintainability
  • 51-70 (Medium): Consider fixing

    • Style inconsistencies
    • Minor code smells
    • Suboptimal patterns
  • 0-50 (Low): Optional improvements

    • Nitpicks
    • Preferences
    • Future considerations
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. 3d ago First seen · 106 lines · 16 tokens per session scan A 927e83b64441

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository tommymorgan/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 540 once invoked, about $0.0001 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.