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 skills add duthaho/claudekit --skill plan-reviewgit clone --depth 1 https://github.com/duthaho/claudekitWrote 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/duthaho/claudekit/plan-review)<a href="https://agentmods.dev/skills/duthaho/claudekit/plan-review"><img src="https://agentmods.dev/badge/skills/duthaho/claudekit/plan-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/duthaho/claudekit/plan-review"><img src="https://agentmods.dev/badge/skills/duthaho/claudekit/plan-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00095 | $0.02685 |
| Opus 5 | $0.00048 | $0.01342 |
| Sonnet 5 | $0.00019 | $0.00537 |
| Haiku 4.5 | $0.00010 | $0.00268 |
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 9d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Review
Overview
The plan-review orchestrator. Dispatches plan-review-architecture and
plan-review-experience in parallel, collects scored findings from each (0-10
on five sub-dimensions), consolidates them into a single ranked fix list, asks
the user to approve fixes, and applies the approved ones to the plan file. The
skill exists because plans fail in two distinct directions — architectural
soundness (data flow, failure modes, edge cases) and human factors (UX hierarchy,
DX touchpoints, error states) — and a single reviewer rarely covers both well.
Splitting the review into two specialist passes catches more, faster. Used
between write-plan and implementation.
When to Use
- A plan exists at
docs/claudekit/plans/<basename>-plan.md(or equivalent) and implementation hasn't started - A plan has been substantially edited and you want a re-review before merge
- Implementation has started and reviewers have flagged structural issues — back up to plan-review before continuing
When NOT to Use
- The change is Trivial or Small (see README "Sizing the work") — plan-review is a Standard-tier step; smaller changes go straight to implementation and
code-review-loop - A previous plan-review already passed and the plan hasn't changed since
- You don't have a written plan yet (use
write-planfirst)
Process
Effort tier: plan-review is a Standard-tier gate — it earns its cost when a
plan carries real design decisions across multiple files. Trivial and Small
changes skip it; their safety net is verification-gate plus code-review-loop on
the diff, which never skip regardless of tier. Reviewing a one-task plan is the kind
of ceremony that teaches people to route around the gates that matter.
Step 1: Locate and read the plan
Goal: Confirm the plan file exists and meets the minimum bar to be reviewed.
Inputs: A path or filename for the plan.
Actions:
- Find the plan file. Default location:
docs/claudekit/plans/. - Read it end to end.
- Check minimum bar: numbered task list, file paths cited, test commands named,
Acceptance:lines present,## Riskssection present. - If the plan fails the minimum bar, return to
write-plan. Do not run review on an underdeveloped plan — the reviewers will flag the same things in two different voices and waste cycles.
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.
- 9d ago First seen · 191 lines · 95 tokens per session scan A 37238cf7bacb
plan-review is a skill published in the GitHub repository duthaho/claudekit (97 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 2,685 once invoked, about $0.0005 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 skills, from other repositories
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
audio-production
Professional audio production for music, podcasts, and sound design. Use when working with audio recording, mixing, mastering, or sound design for any medium.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
brand-identity
Brand strategy and identity design for businesses and products. Use when creating brand guidelines, developing visual identity systems, or defining brand positioning.