full-review

full-review is a command for Claude Code from wshobson/agents. It costs 24 tokens per session (4,641 once invoked), scanned A, original, MIT.

A code-review coordinator that runs several focused reviews of a change, including architecture, security, performance, testing, and general practices. It saves each review phase and pauses for approval at defined checkpoints.

In plain words
What is it for?
Use it for a structured review of a substantial change when you need separate findings from architecture, security, performance, testing, and best-practice checks.
Why use it?
It brings different review concerns into one ordered process and prevents later checks from relying on incomplete earlier results.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the comprehensive-review plugin — 2 commands, 1 agent shipped together

Good fit Use it for a structured review of a substantial change when you…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/wshobson/agents/full-review
About the project

Agentic Plugin Marketplace is a collection of reusable plugins, agents, skills, commands, and rules for coding-agent tools including Claude Code, Codex CLI, Cursor, OpenCode, Antigravity CLI, and GitHub Copilot. It is for developers assembling agentic workflows across multiple harnesses from shared Markdown sources, and the catalogue entries are examples or subsets of those workflow components.

wshobson/agents · 39,449 stars · on GitHub · sethhobson.com

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.

Clone the repo
git clone --depth 1 https://github.com/wshobson/agents

Made for: Claude Code.

Or install comprehensive-review, the plugin that ships this one along with the rest of its 2 commands, 1 agent.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/wshobson/agents/full-review.svg)](https://agentmods.dev/commands/wshobson/agents/full-review)
Your own site
<a href="https://agentmods.dev/commands/wshobson/agents/full-review"><img src="https://agentmods.dev/badge/commands/wshobson/agents/full-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,641 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00024 $0.04641
Opus 5 $0.00012 $0.02320
Sonnet 5 $0.00005 $0.00928
Haiku 4.5 $0.00002 $0.00464

Measured 3d ago against content hash b51ee69ec266, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/comprehensive-review/commands/full-review.md · 598 lines

How it starts

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

Comprehensive Code Review Orchestrator

CRITICAL BEHAVIORAL RULES

You MUST follow these rules exactly. Violating any of them is a failure.

  1. Execute phases in order. Do NOT skip ahead, reorder, or merge phases.
  2. Write output files. Each phase MUST produce its output file in .full-review/ before the next phase begins. Read from prior phase files -- do NOT rely on context window memory.
  3. Stop at checkpoints. When you reach a PHASE CHECKPOINT, you MUST stop and wait for explicit user approval before continuing. Use the AskUserQuestion tool with clear options.
  4. Halt on failure. If any step fails (agent error, missing files, access issues), STOP immediately. Present the error and ask the user how to proceed. Do NOT silently continue.
  5. Use only local agents. All subagent_type references use agents bundled with this plugin or general-purpose. No cross-plugin dependencies.
  6. Never enter plan mode autonomously. Do NOT use EnterPlanMode. This command IS the plan -- execute it.

Pre-flight Checks

Before starting, perform these checks:

1. Check for existing session

Check if .full-review/state.json exists:

  • If it exists and status is "in_progress": Read it, display the current phase, and ask the user:

    Found an in-progress review session:
    Target: [target from state]
    Current phase: [phase from state]
    
    1. Resume from where we left off
    2. Start fresh (archives existing session)
    
  • If it exists and status is "complete": Ask whether to archive and start fresh.

2. Initialize state

Create .full-review/ directory and state.json:

{
  "target": "$ARGUMENTS",
  "status": "in_progress",
  "flags": {
    "security_focus": false,
    "performance_critical": false,
    "strict_mode": false,
    "framework": null
  },
  "current_step": 1,
  "current_phase": 1,
  "completed_steps": [],
  "files_created": [],
  "started_at": "ISO_TIMESTAMP",
  "last_updated": "ISO_TIMESTAMP"
}

Parse $ARGUMENTS for --security-focus, --performance-critical, --strict-mode, and --framework flags. Update the flags object accordingly.

Read the full file on GitHub · 598 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 · 598 lines · 24 tokens per session scan A b51ee69ec266

Subscribe to this mod's changes

full-review is a command published in the GitHub repository wshobson/agents (39,449 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 4,641 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-09-03.