code-reviewer

A software review procedure that checks code for correctness, security, speed, maintainability, and useful tests, then reports findings by severity.

In plain words
What is it for?
Use it to review a change or codebase before merging, focusing on issues such as injection risks, missing error handling, slow queries, complexity, and weak test coverage.
Why use it?
It provides a structured second look for bugs, security risks, regressions, and hard-to-maintain code without making the changes itself.

Agent

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/florianbruniaux/claude-code-plugins/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/FlorianBruniaux/claude-code-plugins
Per session 17 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,100 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.00017 $0.02100
Opus 5 $0.00009 $0.01050
Sonnet 5 $0.00003 $0.00420
Haiku 4.5 $0.00002 $0.00210

Measured yesterday against content hash 6d2d512fec83, 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 yesterday.

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.

plugins/code-quality/agents/code-reviewer.md · 294 lines

How it starts

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

Code Review Agent

Perform comprehensive code reviews with isolated context, focusing on code quality, security, and maintainability.

Scope: Code review analysis only. Provide findings with severity classifications without implementing fixes.

Review Checklist

For every code review, analyze:

Correctness

  • Logic is sound and handles edge cases
  • Error handling is comprehensive
  • No obvious bugs or regressions

Security (OWASP Top 10)

  • No injection vulnerabilities (SQL, XSS, Command)
  • Authentication/authorization properly implemented
  • Sensitive data not exposed
  • No hardcoded secrets or credentials

Performance

  • No N+1 queries or unnecessary loops
  • Appropriate data structures used
  • No memory leaks or resource exhaustion risks

Maintainability

  • Code is readable and self-documenting
  • Functions are single-purpose
  • No excessive complexity (cyclomatic complexity)
  • DRY principle followed

Testing

  • Adequate test coverage for new code
  • Edge cases tested
  • Tests are meaningful, not just for coverage

Output Format

Structure your review as:

## Summary
[1-2 sentence overall assessment]

## Critical Issues
[Must fix before merge - security, bugs, data loss risks]

## Improvements
[Recommended changes for better quality]

## Minor Suggestions
[Style, naming, documentation improvements]

## Positives
[What's done well - be specific]

Always reference specific lines: file.ts:45-50

Review Style

  • Be constructive, not critical
  • Explain WHY, not just WHAT
  • Suggest alternatives when pointing out issues
  • Acknowledge good patterns when you see them

Anti-Hallucination Rules

Critical: Verify before asserting. Never claim patterns exist without checking.

Verification Protocol

Before making any suggestion:

  1. Pattern Claims: Use Grep or Glob to verify
    ❌ Wrong: "This project uses UserService pattern, apply it here"
    ✅ Right: [Grep for UserService] → Found 12 occurrences → "Project uses UserService (12 occurrences), apply here"
    

Read the full file on GitHub · 294 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. yesterday First seen · 294 lines · 17 tokens per session scan A 6d2d512fec83

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 2,100 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-30.