plan

plan is a command for Claude Code from stefan-jansen/claude-code-toolkit. It costs 8 tokens per session (499 once invoked), scanned A, original, MIT.

A planning command that turns requirements or an issue into an ordered list of implementation tasks and dependencies.

In plain words
What is it for?
Use it to plan features, bug fixes, integrations, tests, and documentation from written requirements, an issue, or the current work context.
Why use it?
It helps break large work into clear, testable pieces and shows which tasks must happen first.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the workflow plugin — 6 commands shipped together

Good fit Use it to plan features, bug fixes, integrations, tests, and documentation from written requirements, an issue, or the current work context.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/stefan-jansen/claude-code-toolkit/plan
Install

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.

Clone the repo
git clone --depth 1 https://github.com/stefan-jansen/claude-code-toolkit

Made for: Claude Code.

Or install workflow, the plugin that ships this one along with the rest of its 6 commands.

Wrote 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.

agentmods badge for plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/plan/github.svg)](https://agentmods.dev/commands/stefan-jansen/claude-code-toolkit/plan)
Your own site
<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.

agentmods 80×15 button for plan

Your own site · 80×15
<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>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 499 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash 3de70af71822, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

plugins/workflow/commands/plan.md · 89 lines

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 issue
  • description: Plan from provided text
  • (empty): Plan for active work unit

Process

  1. Validate Context

    • Check for active work unit in .claude/work/ACTIVE_WORK
    • Verify requirements.md exists
    • Warn if overwriting existing plan
  2. Analyze Requirements

    • Identify core functionality
    • Map integration points
    • Define quality requirements
    • Use Sequential Thinking for complex analysis
  3. Create Task Breakdown

    • 2-4 hours per task
    • Single responsibility per task
    • Clear acceptance criteria
    • Testable outcomes
  4. Sequence Tasks

    • Map dependencies (no circular refs)
    • Identify parallel opportunities
    • Define critical path
  5. 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

Changes

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.

  1. 1mo ago First seen · 89 lines · 8 tokens per session scan A 3de70af71822

Subscribe to this mod's changes

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.