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/stefan-jansen/claude-code-toolkitWrote 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/stefan-jansen/claude-code-toolkit/plan)<a href="https://agentmods.dev/commands/stefan-jansen/claude-code-toolkit/plan"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/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/stefan-jansen/claude-code-toolkit/plan"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/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.00008 | $0.00499 |
| Opus 5.5 | $0.00003 | $0.00200 |
| Sonnet 5.5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
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.
What it actually says
Implementation Planning
Create comprehensive task breakdown from requirements.
Input: $ARGUMENTS
Sources
--from-requirements: Use existing requirements.md--from-issue #123: Plan for GitHub issuedescription: Plan from provided text- (empty): Plan for active work unit
Process
-
Validate Context
- Check for active work unit in
.claude/work/ACTIVE_WORK - Verify
requirements.mdexists - Warn if overwriting existing plan
- Check for active work unit in
-
Analyze Requirements
- Identify core functionality
- Map integration points
- Define quality requirements
- Use Sequential Thinking for complex analysis
-
Create Task Breakdown
- 2-4 hours per task
- Single responsibility per task
- Clear acceptance criteria
- Testable outcomes
-
Sequence Tasks
- Map dependencies (no circular refs)
- Identify parallel opportunities
- Define critical path
-
Generate Outputs
Task Sizing
| Type | Scope |
|---|---|
| Foundation | Setup, infrastructure, core architecture |
| Feature | User-facing functionality |
| Integration | External systems, APIs |
| Testing | Test implementation |
| Documentation | Guides, API docs |
Output Files
state.json:
{
"status": "planning_complete",
"current_task": null,
"tasks": [
{
"id": "TASK-001",
"title": "Setup foundation",
"type": "foundation",
"status": "pending",
"dependencies": [],
"acceptance_criteria": ["..."],
"estimated_hours": 3,
"priority": "high"
}
],
"completed_tasks": [],
"next_available": ["TASK-001"]
}
implementation-plan.md: Human-readable plan with:
- Project overview and scope
- Technical architecture
- Task execution plan
- Quality assurance strategy
Next Steps
After planning: Run /next to start first task
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 · 89 lines · 8 tokens per session scan A 3de70af71822
plan is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (90 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 499 once invoked, about $0.0000 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
workflow-classify
Classify task size (S/M/L/XL) and recommend the appropriate workflow pipeline.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
sonarqube
Analyze SonarCloud quality issues for a specific PR.
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
refactor
Analyze code for SOLID violations and suggest targeted improvements.