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/nicobailon/visual-explainer/plan-reviewgit clone --depth 1 https://github.com/nicobailon/visual-explainerWhat 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 | $0.00012 | $0.00484 |
| Opus 5 | $0.00006 | $0.00242 |
| Sonnet 5 | $0.00002 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
plan-review 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.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load the visual-explainer skill and generate a self-contained HTML plan review.
Quick mode
Only use quick mode when $@ contains the literal --quick flag. Remove the flag before resolving the plan input. Complete the same code research and verification below, then read ./quick/README.md and ./quick/schema.json and express the review as a compact spec. In Pi, call visual_explainer with action: "render_quick". In other harnesses, run the local ./quick/render.mjs fallback. If the review does not fit the schema, validation fails, or rendering errors, generate complete HTML and use the normal render flow. Without --quick, preserve full HTML behavior.
Inputs
Use $@ as the plan path or plan text. If no path is given, ask for the plan.
Data gathering before HTML
Read the plan in full. Extract goals, assumptions, proposed files/functions/types, migrations, tests, rollout/release notes, and explicit risks. Read every referenced file, plus importers/dependents that may be affected. Use ripgrep for existing patterns, similar implementations, public API boundaries, config/schema files, and tests.
Source verification
For each proposed change, verify whether referenced files/functions/types exist, whether current behavior matches the plan, what ripple effects are missing, and whether the proposed test coverage fits the current test style. Cite plan sections and file:line evidence.
Required page sections
- Plan summary: problem, core idea, scope.
- Accuracy verdict: correct, stale, risky, unsupported, missing.
- Current architecture: diagram of affected subsystem only.
- Proposed architecture: matching visual diff against current state.
- Gap/risk matrix: correctness, tests, API, data model, UX, security/privacy, performance, maintainability, release.
- File-by-file review: proposed edits, current reality, recommendation.
- Better plan: concrete corrections or simplifications.
- Decision: approve, revise, or reject with rationale.
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.
- 2d ago First seen · 38 lines · 12 tokens per session scan A 82273e0c12d1
plan-review is a command published in the GitHub repository nicobailon/visual-explainer (9,621 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 484 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.