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 commands/yannmenec/inspectrum/review-plangit clone --depth 1 https://github.com/yannmenec/inspectrumWrote 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/commands/yannmenec/inspectrum/review-plan)<a href="https://agentmods.dev/commands/yannmenec/inspectrum/review-plan"><img src="https://agentmods.dev/badge/commands/yannmenec/inspectrum/review-plan.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.00012 | $0.00401 |
| Opus 5 | $0.00006 | $0.00200 |
| Sonnet 5 | $0.00002 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
review-plan 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.
What it actually says
Take the plan you just produced (the most recent ExitPlanMode argument, or
the visible plan in this conversation) and call
mcp__inspectrum__review_plan with:
plan: the full plan markdownreviewers: if$ARGUMENTSis non-empty, split on commas, trim each item, and pass as a string array (e.g.codex,gemini→["codex","gemini"]); otherwise omit the field to use the user's~/.inspectrum/config.tomldefaultsjudge:true
The tool returns structuredContent with the typed result (verdict,
report_markdown, findings, optional revised_plan, session_id, session_path).
Render report_markdown verbatim. If verdict === "revise" and
revised_plan is non-empty, ask: "Apply the revised plan?".
Also recognize the natural-language trigger when the user types something like "review this plan with inspectrum" (with or without a reviewer list). Treat that as the same invocation as the slash command.
Prefer the inspectrum plugin for automatic plan-mode review (hook +
/inspectrum:review):
claude plugin marketplace add yannmenec/inspectrum && claude plugin install inspectrum@inspectrum
Auto-run snippet (optional)
Paste into your project's CLAUDE.md to call review_plan on every plan
without asking:
Before finalizing any plan (Plan Mode or otherwise), call the
`review_plan` MCP tool (inspectrum) with reviewers of your choice.
Skip this step only if the user explicitly says "no review".
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 · 42 lines · 12 tokens per session scan A ec4fec4de5e2
review-plan is a command published in the GitHub repository yannmenec/inspectrum (2 stars, last pushed 26d ago), licensed MIT. It adds 12 tokens to every session and 401 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.
Other commands, from other repositories
coder-eval-implement-plan
Implement an approved codereval plan phase by phase with risk-scaled per-phase review, then a final code review.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
handoff
Export a Waybill Bundle by default, or import one when requested.
harness-adopt
Apply Harness Starter Kit to the current target repository with the prompt-first adoption workflow.
next
You just finished a slash command or a batch of work. The user monitors via Farmer on their phone and cannot see CLI text output.
aitask-explore
Explore the codebase interactively, then create a task for implementation.