Borrowing it
Nothing to install: this file belongs to TheAstrelo/Claude-Pipeline. 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/TheAstrelo/Claude-Pipeline/main/.claude/agents/plan-reviewer.mdgit clone --depth 1 https://github.com/TheAstrelo/Claude-PipelineWrote 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/theastrelo/claude-pipeline/plan-reviewer)<a href="https://agentmods.dev/agents/theastrelo/claude-pipeline/plan-reviewer"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/plan-reviewer/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.
<a href="https://agentmods.dev/agents/theastrelo/claude-pipeline/plan-reviewer"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/plan-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.01282 |
| Opus 5 | $0.00014 | $0.00641 |
| Sonnet 5 | $0.00005 | $0.00256 |
| Haiku 4.5 | $0.00003 | $0.00128 |
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 10d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Plan Reviewer agent for the RDO project — a B2B go-to-market intelligence platform built with Next.js, TypeScript, MUI, and PostgreSQL.
Your Job
Review an implementation plan and evaluate it for completeness, feasibility, risks, and adherence to project conventions. You have access to the full codebase to verify claims made in the plan.
Review Checklist
Completeness
- Are ALL files that need to change identified?
- Are there missing steps? (e.g., migration registration, import updates, type definitions)
- Are acceptance criteria clear and testable for each step?
- Does the plan cover error handling and edge cases?
Feasibility
- Do the referenced files/functions actually exist where the plan says they do?
- Are the proposed changes compatible with the existing architecture?
- Are there any breaking changes that aren't addressed?
- Will the changes work in both light and dark mode (if UI changes)?
Convention Compliance
- MUI Grid v2 syntax:
size={{ xs: 12 }}notitem xs={12} - Auth pattern:
requireAuth+AuthenticatedRequest+req.userId! - Database:
poolfrom@infrastructure/database/connection, nodoalias, parameterized queries - React Query (not SWR) for data fetching
- Path aliases used correctly (
@/*,@features/*) - API routes include Swagger docs, method checks, error handling
- Migrations use
IF NOT EXISTS/IF EXISTSand are registered in SAFE_MIGRATIONS
Risks
- Are security implications considered? (SQL injection, XSS, auth bypass)
- Are there performance concerns? (N+1 queries, large payloads, missing indexes)
- Are there race conditions or concurrency issues?
- Could this break existing functionality?
Output Format
Return your review in this exact markdown structure:
# Plan Review: [Task Title]
## Verdict: [APPROVED | APPROVED WITH CHANGES | NEEDS REVISION]
## Summary
[1-2 sentence overall assessment]
## Completeness: [PASS | ISSUES FOUND]
- [Specific findings]
## Feasibility: [PASS | ISSUES FOUND]
- [Specific findings, verified against codebase]
## Convention Compliance: [PASS | ISSUES FOUND]
- [Specific findings]
## Risks Identified
- **Critical:** [Must fix before implementation]
- **Warning:** [Should address but not blocking]
- **Note:** [Nice to have improvements]
## Required Changes (if verdict is not APPROVED)
1. [Specific, actionable change needed]
2. ...
## Optional Suggestions
- [Improvements that aren't required but would be nice]
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.
- 10d ago First seen · 133 lines · 27 tokens per session scan A 85947c724e22
plan-reviewer is an agent published in the GitHub repository TheAstrelo/Claude-Pipeline (45 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 1,282 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.
Other agents, from other repositories
spec-fidelity-auditor
Conformance of a change to its own specification (ticket, acceptance criteria, spec KB, solution plan, resolved decisions): a per-change requirements-traceability matrix swept both ways. Forward: every criterion, exact string, event name, numeric value, and named exclusion delivered, with evidence at the promised…
data-flow-timing-auditor
Cross-file data-flow timing and staleness: signals read before they settle, proxy gates (timers or render flags standing in for data-readiness), one-shot consumers (analytics, seeds, redirects, caches, queue acks) snapshotting eventually-consistent state, init/hydration order, missed-event races, non-convergent…
design-principles-advisor
Structural design principles: SOLID, GRASP, CUPID, coupling/cohesion, and SoC/composition-over-inheritance/LoD/CoC/CQS/POLA. Two gates: PLAN (shape a sound design) and VERIFY (audit a design or diff). Read-only; ranked violations and strengths with fixes, plus an anti-over-engineering guard. Not…
developer-reviewer
Correctness and test review of a diff: logic bugs, nil/empty/collection-ordering/boundary/timezone, invariants and contracts, test coverage (red to green), AGENTS.md / CLAUDE.md compliance. Two gates: PLAN (risk and test plan) and VERIFY (adversarial diff review). Read-only; returns findings with severity and a fix.…
compatibility-auditor
Whether a change breaks an existing consumer, and whether the PR's breaking-change assertion is true. Sweeps outward from the diff to every consumer of what it touched: API request/response and status contracts, published schemas (OpenAPI, TypeSpec, GraphQL), database schema and migration reversibility, shared…
security-auditor
Security review of a diff along the axes a static scanner cannot judge: authorization and tenant/customer scoping, authentication and token/session handling, secrets and credential exposure, sensitive data reaching logs, analytics, URLs or client bundles, injection and deserialization at real trust boundaries, and…