A command that creates an implementation plan for a requested change and has separate planning reviewers check and revise it for up to three rounds. A plan review is a structured check of proposed files, design choices, and tests before coding.

Use it when a task needs a reviewed step-by-step plan covering files, architecture, tradeoffs, tests, and open questions.

It can expose incorrect assumptions about the codebase and improve the plan before implementation begins.

plan-review — Command for Claude Code by andrei-isvoran96

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/andrei-isvoran96/claude-skill-lab

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/andrei-isvoran96/claude-skill-lab/plan-review/github.svg)](https://agentmods.dev/commands/andrei-isvoran96/claude-skill-lab/plan-review)

Your own site

<a href="https://agentmods.dev/commands/andrei-isvoran96/claude-skill-lab/plan-review"><img src="https://agentmods.dev/badge/commands/andrei-isvoran96/claude-skill-lab/plan-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/andrei-isvoran96/claude-skill-lab/plan-review"><img src="https://agentmods.dev/badge/commands/andrei-isvoran96/claude-skill-lab/plan-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 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,013 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01013
Opus 5.5	$0.00000	$0.00405
Sonnet 5.5	$0.00000	$0.00203
Haiku 4.5	$0.00000	$0.00101

Measured 2mo ago against content hash d071d1361c7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan-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 2mo 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.

commands/plan-review.md · 72 lines

How it starts

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

Draft an implementation plan for the user's request, then run up to 3 rounds of unbiased review by a fresh Plan subagent, revising between rounds.

The user's request: $ARGUMENTS

Procedure

Step 1 — Draft the initial plan

Spawn a Plan subagent to produce the first draft. Give it only the user's request above (no prior conversation). Ask for a step-by-step implementation plan: critical files, changes per file, architectural tradeoffs, test strategy, and any open questions.

Store the returned plan as PLAN_V1.

Step 2 — Round 1 review (always run)

Spawn a fresh Plan subagent as reviewer. It must not see your drafting reasoning or the parent conversation — only what you put in its prompt. CLAUDE.md is auto-loaded, so the reviewer already knows the architecture, commands, and coding standards.

The reviewer prompt must include:

The user's original request (verbatim: $ARGUMENTS)
The full plan text (PLAN_V1)
Instruction to verify claims against the real code — Read/Grep the codebase to check that referenced files, services, and patterns actually exist and are the right home for the changes. Do not judge on vibes.
Review rubric:
- Correctness: will this actually solve the user's request?
- Missing edge cases or error paths
- Scope: anything added beyond what was asked? Anything required but missing?
- Architectural fit: matches existing patterns?
- Testability and test coverage
- Adherence to the project's CLAUDE.md coding standards
Required output contract — the reviewer MUST start its response with one of exactly two tokens on the first line:
- APPROVED — no substantive issues, plan is ready to execute
- NEEDS_CHANGES — followed by itemized issues (severity: critical/warning/nitpick, with file:line references where applicable)
Nitpick-only findings still count as APPROVED — only critical/warning issues warrant NEEDS_CHANGES.

Step 3 — Decide whether to iterate

Read the full file on GitHub · 72 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.

2mo ago First seen · 72 lines · 0 tokens per session scan A d071d1361c7e

Subscribe to this mod's changes

plan-review is a command published in the GitHub repository andrei-isvoran96/claude-skill-lab (1 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,013 tokens. 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-31.

Planning

plan-review next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
plan-reviewandrei-isvoran96/claude-skill-lab	Command	1	5mo ago	MIT	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code