plan-document-reviewer

An automated reviewer for implementation plans. It checks whether a plan covers the requirements, breaks work into actionable tasks, and can be followed without getting stuck.

In plain words
What is it for?
Use it to review plans for completeness, alignment with a specification, sensible task boundaries, and practical buildability.
Why use it?
It catches missing steps, unfinished placeholders, scope drift, or vague tasks before implementation begins. Finding these problems early reduces rework.

Agent

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/chinkan/rustfox/plan-document-reviewer
Clone the repo
git clone --depth 1 https://github.com/chinkan/RustFox
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 245 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.00018 $0.00245
Opus 5 $0.00009 $0.00122
Sonnet 5 $0.00004 $0.00049
Haiku 4.5 $0.00002 $0.00024

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

Security

Grade A, and why

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

.opencode/agents/plan-document-reviewer.md · 35 lines

What it actually says

You are a plan document reviewer. Verify the plan is complete, matches the spec, and has proper task decomposition.

What to Check:

Category What to Look For
Completeness TODOs, placeholders, incomplete tasks, missing steps
Spec Alignment Plan covers spec requirements, no major scope creep
Task Decomposition Tasks have clear boundaries, steps are actionable
Buildability Could an engineer follow this plan without getting stuck?

Calibration: Only flag issues that would cause real problems during implementation. An implementer building the wrong thing or getting stuck is an issue. Minor wording is not.

Output Format:

Plan Review

Status: Approved | Issues Found

Issues (if any):

  • [Task X, Step Y]: [specific issue] - [why it matters]

Recommendations (advisory):

  • [suggestions for improvement]
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 · 35 lines · 18 tokens per session scan A ac0e09e5c3d8

Subscribe to this mod's changes

plan-document-reviewer is an agent published in the GitHub repository chinkan/RustFox (7 stars, last pushed 26d ago), licensed MIT. It adds 18 tokens to every session and 245 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-31.

Related

Other agents, from other repositories

codemap

Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…

alvinunreal/oh-my-opencode-slim · 0 tokens

api-designer

REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.

AgentWorkforce/relay · 35 tokens

shep-web-route-creator

Scaffolds ONE new Next.js API route under src/presentation/web/app/api/, wires it to an existing use case via resolve(), handles the canonical error-to-HTTP mapping, and keeps presentation thin. Use when a use case already exists and the caller needs a web endpoint exposing it. Does NOT create the use case, does NOT…

shep-ai/shep · 85 tokens

python-pro

Python 3.13 language expert for the ClosedLoop plugin monorepo. Reviews implementation plans for type annotation correctness, argparse CLI conventions, import isolation, fail-open/fail-closed boundary patterns, and pyright/ruff compliance. Produces type-patterns.md in legacy mode.

closedloop-ai/claude-plugins · 60 tokens

Audit

Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…

BlackBeltTechnology/pi-agent-dashboard · 98 tokens

answered-questions-subagent

Processes answered questions from plan.json and incorporates them into relevant tasks.

closedloop-ai/claude-plugins · 19 tokens