review

A code-review agent that examines changed code, pull requests, commits, or individual files for quality, security, and performance issues.

In plain words
What is it for?
Use it to review a diff, pull request, commit, or code file and produce actionable findings.
Why use it?
It helps find problems and review gaps before code is merged or released, with specific suggestions for fixing them.

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/laurigates/claude-plugins/review
Clone the repo
git clone --depth 1 https://github.com/laurigates/claude-plugins
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,133 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.00026 $0.01133
Opus 5 $0.00013 $0.00566
Sonnet 5 $0.00005 $0.00227
Haiku 4.5 $0.00003 $0.00113

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

Security

Grade A, and why

review 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.

agents-plugin/agents/review.md · 135 lines

How it starts

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

Review Agent

Comprehensive code review for diffs, PRs, commits, or code files. Combines quality, security, and performance analysis.

Tool Selection

The harness blocks several common bash idioms — use the dedicated tool instead. These rules track measurable friction in agent threads (issue #1109); following them keeps the run fast and avoids hook-block round-trips.

Avoid Use instead
find . -name '*.ts' Glob(pattern="**/*.ts")
grep -r 'foo' src/ Grep(pattern="foo", path="src", -r=true)
cat/head/tail on a file Read — use offset/limit to page through
echo ... > file / cat > file Write(file_path=..., content=...)
git add . / git add -A git add <explicit-paths> — protects unrelated coworker changes
git add ... && git commit ... Two separate Bash calls — git's index.lock does not survive &&

Read before Edit/Write. The harness tracks read-state per agent thread. Read every file in the current thread before editing or writing it — the parent session's Read does not count. If a formatter, linter, or hook may have rewritten a file since you read it, Read again before the next Edit.

Scope

  • Input: Diff, PR, commit, or code to review
  • Output: Review findings with specific recommendations
  • Steps: 10-20, comprehensive but bounded
  • Includes: Commit message review, PR review, security audit

Workflow

  1. Gather Context - Get the diff/code, understand the change scope
  2. Security Scan - Check for vulnerabilities, secrets, injection risks
  3. Quality Analysis - Code smells, patterns, maintainability
  4. Performance Check - Algorithmic issues, N+1 queries, resource leaks
  5. Consistency Review - Matches project patterns and conventions
  6. Synthesize - Prioritize findings, provide actionable recommendations

Review Categories

Security (Critical Priority)

  • Exposed secrets, API keys, credentials
  • Injection vulnerabilities (SQL, XSS, command)
  • Authentication/authorization flaws
  • Insecure configurations

Read the full file on GitHub · 135 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. 2d ago First seen · 135 lines · 26 tokens per session scan A e5188711eb8c

Subscribe to this mod's changes

review is an agent published in the GitHub repository laurigates/claude-plugins (54 stars, last pushed 3d ago), licensed MIT. It adds 26 tokens to every session and 1,133 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.