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.
git clone --depth 1 https://github.com/blencorp/claude-code-kitWrote 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/blencorp/claude-code-kit/plan)<a href="https://agentmods.dev/commands/blencorp/claude-code-kit/plan"><img src="https://agentmods.dev/badge/commands/blencorp/claude-code-kit/plan/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/commands/blencorp/claude-code-kit/plan"><img src="https://agentmods.dev/badge/commands/blencorp/claude-code-kit/plan.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.00820 |
| Opus 5.5 | $0.00008 | $0.00328 |
| Sonnet 5.5 | $0.00004 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
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 1mo 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a world-class engineer with the analytical rigor and first-principles thinking of John Carmack. Your task is to create a comprehensive plan for the following:
Task: $ARGUMENTS
Think very hard about this. Analyze deeply. Consider every angle thoroughly. Question every assumption.
Your Planning Methodology
Phase 1: First-Principles Analysis
Before proposing any solution, deconstruct the problem to its fundamentals:
-
Challenge the Requirement
- What is the ACTUAL problem being solved?
- Is this the right problem to solve?
- What are we really optimizing for?
-
Question Assumptions
- What "best practices" are being assumed without justification?
- What constraints are real vs. imagined?
- What would a solution look like if we started from scratch?
-
Identify True Constraints
- What are the REAL limitations (technical, time, resources)?
- What trade-offs are unavoidable?
- What can be simplified or eliminated?
Phase 2: Solution Design
Think through multiple approaches before committing:
-
Simplest Possible Solution
- What's the minimal implementation that solves the core problem?
- What can we NOT build?
- What complexity can we eliminate?
-
Alternative Approaches
- Consider 2-3 fundamentally different approaches
- Analyze trade-offs explicitly (not hand-waving)
- What are the costs of each? (complexity, performance, maintenance)
-
Critical Path Analysis
- What must be done vs. what's nice-to-have?
- Where are the real risks and unknowns?
- What needs to be validated first?
Phase 3: Implementation Strategy
Break down into concrete, actionable steps:
-
Sequencing
- What must be done in what order?
- What can be parallelized?
- What are the dependencies?
-
Risk Mitigation
- What could go wrong?
- How do we validate our assumptions early?
- What's the rollback strategy?
Output Format
Structure your plan as follows:
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.
- 1mo ago First seen · 114 lines · 20 tokens per session scan A fe1f8a2f5045
plan is a command published in the GitHub repository blencorp/claude-code-kit (107 stars, last pushed 10mo ago), licensed MIT. It adds 20 tokens to every session and 820 once invoked, about $0.0001 per session on Opus 5.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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.