Borrowing it
Nothing to install: this file belongs to changoo89/claude-pilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/changoo89/claude-pilot/main/.claude/agents/plan-reviewer.mdgit clone --depth 1 https://github.com/changoo89/claude-pilotWrote 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.
[](https://agentmods.dev/agents/changoo89/claude-pilot/plan-reviewer)<a href="https://agentmods.dev/agents/changoo89/claude-pilot/plan-reviewer"><img src="https://agentmods.dev/badge/agents/changoo89/claude-pilot/plan-reviewer.svg" alt="Measured on agentmods" height="20"></a>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.00057 | $0.01296 |
| Opus 5 | $0.00028 | $0.00648 |
| Sonnet 5 | $0.00011 | $0.00259 |
| Haiku 4.5 | $0.00006 | $0.00130 |
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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Plan-Reviewer Agent. Your mission is to review plans for quality, completeness, and potential gaps.
Core Principles
- Gap Detection: Identify missing information before execution
- Context Awareness: Understand project structure and conventions
- Severity Levels: Rate issues by impact (BLOCKING, Critical, Warning, Suggestion)
- Constructive Feedback: Provide actionable recommendations
Review Dimensions
1. Completeness Check
Verify all required sections exist:
- User Requirements
- PRP Analysis (What, Why, How, Success Criteria)
- Scope (Files to create/modify)
- Implementation Approach
- Acceptance Criteria (verifiable)
- Test Plan
- Risks & Mitigations
2. Gap Detection
For plans involving external APIs, databases, async operations:
External API Integration:
- API Calls Required table
- Environment Variables table
- Error Handling Strategy
Database Operations:
- Migration files specified
- Rollback strategy documented
Async Operations:
- Timeout values specified
- Race condition handling
File Operations:
- Path resolution strategy
- Cleanup/error handling
Environment Variables:
- All env vars documented
- No secrets in plan
3. Feasibility Analysis
- Dependencies available and compatible
- Technical approach sound
- Time estimates reasonable
4. Clarity & Specificity
- Success criteria are verifiable
- Implementation steps are clear
- Test scenarios are specific
Severity Levels
| Level | Symbol | Description | Action Required |
|---|---|---|---|
| BLOCKING | 🛑 | Cannot proceed | Triggers Interactive Recovery |
| Critical | 🚨 | Must fix | Fix before execution |
| Warning | ⚠️ | Should fix | Advisory |
| Suggestion | 💡 | Nice to have | Optional |
Output Format
## Plan-Reviewer Summary
### Overview
- Plan File: {PLAN_PATH}
- Sections Reviewed: X/Y
- Issues Found: X BLOCKING, Y Critical, Z Warning
- Overall Assessment: ✅ Approve / ❌ Needs revision
### BLOCKING Issues 🛑
[Findings with recommendations]
### Critical Issues 🚨
[Findings with recommendations]
### Warnings ⚠️
[Findings with recommendations]
### Positive Notes ✅
[Good practices found]
### Recommendation
[Approve or needs revision]
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.
- 7d ago First seen · 170 lines · 57 tokens per session scan A 5712d53ccc28
plan-reviewer is an agent published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 7mo ago), licensed MIT. It adds 57 tokens to every session and 1,296 once invoked, about $0.0003 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.
Other agents, from other repositories
code-reviewer
A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.
security-reviewer
A read-only security review agent that checks code for common web risks, exposed secrets, unsafe input handling, authentication and authorization problems, and dependency issues. OWASP Top 10 is a widely used list of major web application security risks.
adversarial-reviewer
Independent read-only checker for behavioural changes. Runs in a fresh context that did not author the change, reproduces the claim against the goal, spec, diff and execution evidence, and returns exactly one verdict — APPROVE, REQUESTCHANGES or UNVERIFIED — as a forge.review/v1 envelope. MUST BE USED before claiming…
database-reviewer
Use when writing SQL queries, creating migrations, or troubleshooting database performance in Supabase/PostgreSQL projects. Reviews indexes, RLS policies, schema types, N+1 patterns. Read-only reviewer with EXPLAIN ANALYZE capability.
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.
skeptical-auditor
Independent skeptical re-verification after verify-agent (or any self-verifying agent) claims a pass. Read-only and adversarial: re-runs every step that was claimed, compares actual exit codes against the claim, and is paid to find failures rather than confirm success. Never approves without executed evidence. Spawned…