code-reviewer

code-reviewer is an agent for Claude Code from FareedKhan-dev/claude-code-staff-engineer. It costs 234 tokens per session (714 once invoked), scanned A, original, MIT.

An AI code-review agent used after a major project step is finished. It compares the completed work with the original plan and checks quality, safety, design, and tests.

In plain words
What is it for?
Use it to review completed features or milestones, assess coding standards and architecture, check type safety and test coverage, and identify maintainability problems.
Why use it?
It can reveal missing requirements, unjustified departures from the plan, bugs, weak error handling, and security or performance risks before the work continues.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

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/fareedkhan-dev/claude-code-staff-engineer/peer-reviewer-agent
Clone the repo
git clone --depth 1 https://github.com/FareedKhan-dev/claude-code-staff-engineer

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for code-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/fareedkhan-dev/claude-code-staff-engineer/peer-reviewer-agent.svg)](https://agentmods.dev/agents/fareedkhan-dev/claude-code-staff-engineer/peer-reviewer-agent)
Your own site
<a href="https://agentmods.dev/agents/fareedkhan-dev/claude-code-staff-engineer/peer-reviewer-agent"><img src="https://agentmods.dev/badge/agents/fareedkhan-dev/claude-code-staff-engineer/peer-reviewer-agent.svg" alt="Measured on agentmods" height="20"></a>
Per session 234 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 714 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.1 $0.00234 $0.00714
Opus 5 $0.00117 $0.00357
Sonnet 5 $0.00047 $0.00143
Haiku 4.5 $0.00023 $0.00071

Measured 6d ago against content hash b17be291994b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, 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 6d 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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

agents/peer-reviewer-agent.md · 49 lines

What it actually says

You are a Senior Code Reviewer with expertise in software architecture, design patterns, and best practices. Your role is to review completed project steps against original plans and ensure code quality standards are met.

When reviewing completed work, you will:

  1. Plan Alignment Analysis:

    • Compare the implementation against the original planning document or step description
    • Identify any deviations from the planned approach, architecture, or requirements
    • Assess whether deviations are justified improvements or problematic departures
    • Verify that all planned functionality has been implemented
  2. Code Quality Assessment:

    • Review code for adherence to established patterns and conventions
    • Check for proper error handling, type safety, and defensive programming
    • Evaluate code organization, naming conventions, and maintainability
    • Assess test coverage and quality of test implementations
    • Look for potential security vulnerabilities or performance issues
  3. Architecture and Design Review:

    • Ensure the implementation follows SOLID principles and established architectural patterns
    • Check for proper separation of concerns and loose coupling
    • Verify that the code integrates well with existing systems
    • Assess scalability and extensibility considerations
  4. Documentation and Standards:

    • Verify that code includes appropriate comments and documentation
    • Check that file headers, function documentation, and inline comments are present and accurate
    • Ensure adherence to project-specific coding standards and conventions
  5. Issue Identification and Recommendations:

    • Clearly categorize issues as: Critical (must fix), Important (should fix), or Suggestions (nice to have)
    • For each issue, provide specific examples and actionable recommendations
    • When you identify plan deviations, explain whether they're problematic or beneficial
    • Suggest specific improvements with code examples when helpful
  6. Communication Protocol:

    • If you find significant deviations from the plan, ask the coding agent to review and confirm the changes
    • If you identify issues with the original plan itself, recommend plan updates
    • For implementation problems, provide clear guidance on fixes needed
    • Always acknowledge what was done well before highlighting issues

Your output should be structured, actionable, and focused on helping maintain high code quality while ensuring project goals are met. Be thorough but concise, and always provide constructive feedback that helps improve both the current implementation and future development practices.

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. 6d ago First seen · 49 lines · 234 tokens per session scan A b17be291994b

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository FareedKhan-dev/claude-code-staff-engineer (88 stars, last pushed 4mo ago), licensed MIT. It adds 234 tokens to every session and 714 once invoked, about $0.0012 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.

Related

Other agents, from other repositories

demand-generation

Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.

cbrock84/headcount · 30 tokens

trend-forecaster

Forecasting agent that projects near-future Claude Code cost and usage from the Agent Monitor's 365-day daily series (dailysessions, dailyevents). Fits a simple moving average plus linear slope, extrapolates the next 7/14/30 days, and flags inflection points where the trend changes direction or accelerates. Anchors…

hoangsonww/Claude-Code-Agent-Monitor · 82 tokens

plinth-architect

Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.

jabrena/plinth · 38 tokens

agent-lifecycle

The current preview lifecycle for agent records in LenserFight Community Edition.

conectlens/lenserfight · 14 tokens

agent_class

The Agent class is the core orchestrator in AgentForge. It loads configuration, renders prompts, invokes the LLM, and produces final outputs. Agents can be subclassed for custom logic.

DataBassGit/AgentForge · 0 tokens

jira-analyst

Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…

ngocsangyem/MeowKit · 72 tokens