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 skills/r13v/pi-feature-dev/plan-reviewnpx skills add r13v/pi-feature-dev --skill plan-reviewgit clone --depth 1 https://github.com/r13v/pi-feature-devWrote 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/skills/r13v/pi-feature-dev/plan-review)<a href="https://agentmods.dev/skills/r13v/pi-feature-dev/plan-review"><img src="https://agentmods.dev/badge/skills/r13v/pi-feature-dev/plan-review.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 | $0.00123 | $0.01781 |
| Opus 5 | $0.00062 | $0.00890 |
| Sonnet 5 | $0.00025 | $0.00356 |
| Haiku 4.5 | $0.00012 | $0.00178 |
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 4d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Review
Review the plan before implementation. First verify that it solves the stated problem with the smallest repository-aligned approach. Then assume the plan has already shipped and failed; work backward from repository evidence to explain why.
Remain read-only. Analyze and report; never implement or edit the plan.
Prefix every finding with [plan-review] and identify the affected plan
section or task.
Isolate the Review
Prefer an isolated reviewer when the host agent and active policy support fresh-context, read-only workers or equivalent delegation.
Give the isolated reviewer only:
- The plan path or plan text.
- The original user request, if available.
- The repository root.
- Any explicit review focus from the user.
Do not pass the plan creator's hidden reasoning, conclusions, intended fixes, confidence claims, or prior review commentary.
If isolation is unavailable, perform the review locally. Treat prior planning context as untrusted, reload the plan and relevant project files from disk, and judge the plan against the repository and original request.
Resolve the Review Target
- Review the user-provided plan path or plan text when present.
- Otherwise, list plans in
docs/plans/, excludingcompleted/. - If exactly one current plan exists, review it.
- If multiple plans exist and context does not identify one, ask the user to choose.
- If no plan is available, ask for its path or text.
Build Repository Evidence
Read applicable project guidance such as AGENTS.md, CLAUDE.md, nearby
README files, and contributor documentation. Inspect the code and tests named
by the plan, then read their exports, immediate callers, and shared utilities.
Trace relevant data and control flow to repository boundaries.
Inspect migrations, schemas, configuration, deployment paths, authorization, jobs, queues, caches, and operational documentation only when the planned change can reach them. Prefer active code, tests, ADRs, and contracts over generic best practice or historical precedent.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 188 lines · 123 tokens per session scan A 54c6b8aa9169
plan-review is a skill published in the GitHub repository r13v/pi-feature-dev (2 stars, last pushed 17d ago), licensed MIT. It adds 123 tokens to every session and 1,781 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…