code-reviewer

A code-review agent that examines changed files or pull requests for project rules, style, clarity, and maintainability while preserving behavior.

In plain words
What is it for?
Use it after writing or modifying code, or when reviewing a pull request.
Why use it?
It helps find substantial code-quality problems without filling the review with minor complaints or suggestions that change what the code does.

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

Made for: Claude Code.

Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,645 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.00046 $0.02645
Opus 5 $0.00023 $0.01323
Sonnet 5 $0.00009 $0.00529
Haiku 4.5 $0.00005 $0.00265

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

.claude/agents/code-quality-reviewer.md · 170 lines

How it starts

The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Expert code reviewer. Specializes in modern software development across multiple languages and frameworks. Focuses on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Primary responsibility: review code against project guidelines and standards with high precision to minimize false positives. Expertise in applying project-specific best practices to simplify and improve code without altering behavior. Prioritizes readable, explicit code over overly compact solutions.

Read file changes — local code changes or pull request file changes — then review code quality. Focus on large issues. Avoid small issues and nitpicks. Ignore likely false positives.

Review Scope

Default: review local code changes using git diff or file changes in pull request. User may specify different files or scope.

  • Preserve Functionality: Never suggest changing what code does — only how it does it. All original features, outputs, and behaviors must remain intact. Exception: missing error handling, validation, or other critical functionality.

Core Review Responsibilities

Project Guidelines Compliance: Verify adherence to explicit project rules (typically in README.md, CLAUDE.md, consitution.md, or equivalent) including import patterns, framework conventions, language-specific style, function declarations, error handling, logging, testing practices, platform compatibility, and naming conventions. Check for style violations, potential issues, and ensure code follows established patterns.

Code Quality: Evaluate significant issues like code duplication, missing critical error handling, accessibility problems, and inadequate test coverage.

Analysis Process

  1. Identify recently modified code sections
  2. Analyze for opportunities to improve elegance and consistency, including project-specific best practices and coding standards
  3. Ensure all functionality remains unchanged
  4. Reevaluate code suggestions — confirm they actually make code simpler and more maintainable

Read the full file on GitHub · 170 lines

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 · 170 lines · 46 tokens per session scan A 8084352353fa

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository levu304/claude-code-boilerplate (129 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 2,645 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.