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/reggiechan74/cc-plugins/plan-reviewnpx skills add reggiechan74/cc-plugins --skill plan-reviewgit clone --depth 1 https://github.com/reggiechan74/cc-pluginsWrote 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/reggiechan74/cc-plugins/plan-review)<a href="https://agentmods.dev/skills/reggiechan74/cc-plugins/plan-review"><img src="https://agentmods.dev/badge/skills/reggiechan74/cc-plugins/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.00066 | $0.00770 |
| Opus 5 | $0.00033 | $0.00385 |
| Sonnet 5 | $0.00013 | $0.00154 |
| Haiku 4.5 | $0.00007 | $0.00077 |
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Review: Validate Execution Plans
Purpose
Review and validate execution plans before code changes begin, ensuring plans have clear acceptance criteria, appropriate critic assignments, and realistic scope.
When to Use
- After planner agent creates execution plan
- When user explicitly requests plan review
- Before high-stakes operations (configured in highStakesPatterns)
Validation Criteria
Completeness Checks
✓ Scope defined: Files, operations, and boundaries clear ✓ Success criteria present: At least 3 specific, measurable criteria ✓ Critic assignment: Each criterion mapped to responsible critic ✓ Retry budget set: Escalation path defined ✓ Cost estimate included: Token overhead calculated
Quality Gates
Acceptance criteria must be:
- Specific (not "good code" but "all tests pass, coverage >80%")
- Measurable (binary pass/fail, not subjective)
- Pre-declared (before execution, not emergent)
- Mapped to critics (clear veto authority assignment)
Domain-specific patterns:
- Financial: Must specify precision, rounding method, audit requirements
- Security: Must reference OWASP checklist, auth patterns
- Performance: Must define latency SLAs, memory limits
Review Process
- Parse plan structure - Extract scope, criteria, critics, budget
- Check completeness - Verify all required sections present
- Validate criteria - Ensure specific and measurable
- Verify critic mapping - Each criterion has responsible critic
- Check domain patterns - Apply domain-specific requirements
- Estimate feasibility - Scope appropriate for retry budget
- Present findings - Show issues and recommendations
Example Reviews
Good Plan
EXECUTION PLAN ✓
Scope: Refactor auth to JWT ✓
Files: src/auth/*.ts ✓
SUCCESS CRITERIA: ✓
✓ All 18 existing tests pass (Code Critic validates)
✓ No OWASP Top 10 violations (Security Critic validates)
✓ Token storage uses httpOnly cookies (Security Critic validates)
✓ Token refresh handles 401 (Code Critic validates)
✓ Coverage maintains 85%+ (Code Critic validates)
Critics: code, security ✓
Budget: 6 iterations ✓
Cost: +40% tokens ($0.15) ✓
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 · 106 lines · 66 tokens per session scan A fd914688564e
Plan Review is a skill published in the GitHub repository reggiechan74/cc-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 770 once invoked, about $0.0003 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…