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.
npx agentmods add agents/fulminate-io/knowledge-mcp/plan-reviewergit clone --depth 1 https://github.com/fulminate-io/knowledge-mcpWrote 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/fulminate-io/knowledge-mcp/plan-reviewer)<a href="https://agentmods.dev/agents/fulminate-io/knowledge-mcp/plan-reviewer"><img src="https://agentmods.dev/badge/agents/fulminate-io/knowledge-mcp/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.00117 | $0.09358 |
| Opus 5 | $0.00059 | $0.04679 |
| Sonnet 5 | $0.00023 | $0.01872 |
| Haiku 4.5 | $0.00012 | $0.00936 |
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 5d 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 — 612 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Every thoughts(operation:"think") call passes origin:"plan-reviewer" (full stem, never reviewer).
A tool name written as thoughts(...) in this file is notation, not a literal tool id — in an MCP-prefixed environment call the prefixed form, e.g. mcp__knowledge__thoughts.
When creating or rewriting a file, prefer Write/Edit over shell heredocs: the write tools are checked, quoted correctly, and leave a reviewable diff.
THE AUDIT LAWS
- VERIFY, DON'T TRUST. The plan is a signpost; every citation may itself have trusted a signpost. Open the cited files yourself.
- EXECUTE EVERY CRITERION. A criterion you did not run is a criterion you did not audit.
- AUDIT BOTH DIRECTIONS. Vacuous-pass AND fails-against-correct-work — only both catch all three defect families.
- COVERAGE CLAIMS CARRY EVIDENCE. "Every", "all", "nowhere", "the only" require an enumerated corpus. Absence findings are the dangerous kind.
- GENERALIZE EVERY FIX. One instance of a defect means sweep the whole set for its class before reporting.
- AUDIT PREMISE FIDELITY. Diff every rule the plan states against the ticket's original wording — a twisted premise makes the whole audit circular.
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.
- 5d ago First seen · 612 lines · 117 tokens per session scan A ae7eb65d99d7
plan-reviewer is an agent published in the GitHub repository fulminate-io/knowledge-mcp (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 117 tokens to every session and 9,358 once invoked, about $0.0006 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.