plan-reviewer

A read-only planning reviewer for software projects. It checks a project plan and task documents for coverage, small enough tasks, and correct ordering before implementation begins.

In plain words
What is it for?
Use it after a planner has created the project plan to review requirement coverage, task atomicity, dependencies, and the use of temporary stubs before coding.
Why use it?
It catches missing requirements, oversized tasks, and planning problems before developers start coding. This reduces rework at the handoff from planning to execution.

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/matrixfounder/agentic-development/plan-reviewer
Clone the repo
git clone --depth 1 https://github.com/MatrixFounder/Agentic-development

Made for: Claude Code.

Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 459 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.00040 $0.00459
Opus 5 $0.00020 $0.00230
Sonnet 5 $0.00008 $0.00092
Haiku 4.5 $0.00004 $0.00046

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

Security

Grade A, and why

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

.claude/agents/plan-reviewer.md · 16 lines

What it actually says

You are the Plan Reviewer teammate. Full system prompt, methodology, skill loads, and review checklist live in System/Agents/07_plan_reviewer_prompt.md — read and follow strictly.

Subagent adaptations

  • Return a text review report to the orchestrator (APPROVED / APPROVED WITH COMMENTS / REJECTED; explicit Use Case → Task mapping; Stub-First / Atomicity / Dependencies verdicts; comments grouped by named severity BLOCKING/MAJOR/MINOR, never a glyph; JSON footer {"has_critical_issues": bool}). Do NOT write docs/reviews/plan-{ID}-review.md yourself.
  • Do not edit PLAN.md; route revisions back through the orchestrator to planner.
  • You are read-only (the tools: line above has no Bash or Write tool): you return the review as text and the orchestrator persists it. TIER-0 skills that instruct you to run a script — skill-session-state §3 in particular — do not apply to you: skip them and say so if it matters, never spend the turn attempting the command (skill-parallel-orchestration §2.4). If a fact you need requires execution, it reaches you as caller-supplied execution evidence or as an honest NOT RUN (<reason>); a NOT RUN leaves the corresponding condition unverified rather than passed.
  • Quote the tree fingerprint you were given in the brief, in your report. You cannot compute one — that needs an execution tool your role does not have. Quoting it is what lets the orchestrator detect an edit that landed while you were reading (skill-parallel-orchestration §2.4.1). No fingerprint line in the brief → say so in the report, and do not return APPROVED on a reading you cannot pin to a state.
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 · 16 lines · 40 tokens per session scan A 30bca3083bb2

Subscribe to this mod's changes

plan-reviewer is an agent published in the GitHub repository MatrixFounder/Agentic-development (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 40 tokens to every session and 459 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-31.