create-plan

Important: ALL phases must use checkmarks for their tasks. Each checkmark should correspond to a single commit. The checkmark should be marked - [x] in the same commit that completes the task. Phase tasks should be prefixed with parent phase number and letters (a, b, c, etc.).

Command for Claude Code

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.

agentmods
npx agentmods add commands/bliporg/blip/create-plan
Clone the repo
git clone --depth 1 https://github.com/bliporg/blip

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 643 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00000 $0.00643
Opus 5 $0.00000 $0.00321
Sonnet 5 $0.00000 $0.00129
Haiku 4.5 $0.00000 $0.00064

Measured today against content hash b2ec3740ce67, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-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 today.

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.

.claude/commands/create-plan.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create a plan

Planning System

  1. Plans should be created at plans/<date>-<plan-name>.md (e.g., 2026-01-15-feature-name.md)

  2. Use this format:

    • Clear phases (numbered: 1, 2, 3...)
    • Subtasks within each phase as checkmarks: - [ ] (pending) or - [x] (done)

    Important: ALL phases must use checkmarks for their tasks. Each checkmark should correspond to a single commit. The checkmark should be marked - [x] in the same commit that completes the task. Phase tasks should be prefixed with parent phase number and letters (a, b, c, etc.)

    Example:

    ## Phase 1: One Phase
    - [x] 1a: Some task
    - [x] 1b: Another task
    - [ ] 1c: One more task
    
    ## Phase 2: Another Phase
    - [ ] 2a: Some task
    - [ ] 2b: Another task
    - [ ] 2c: One more task
    
  3. Check previous plans in plans/ and recent commits when creating a plan to see if it builds on previous work.

  4. In some cases, phases or tasks can be done in parallel using parallel agents. Only use this notation when parallelizing is clearly beneficial:

    ## Phase 1: One Phase
    - [x] 1a: Some task
    - [x] 1b: Another task
    - [ ] 1c: One more task
    
    **Parallel Phases: 2,3**
    
    ## Phase 2: Another Phase
    - [ ] 2a: Some task
    
    **Parallel Tasks: 2b, 2c**
    
    - [ ] 2b: Another task
    - [ ] 2c: One more task
    
    ## Phase 3: One More Phase
    - [ ] 3a: Some task
    - [ ] 3b: Another task
    - [ ] 3c: One more task
    

    In this example, phases 2 and 3 can run in parallel. Within phase 2, tasks 2b and 2c can also run in parallel. Add blank lines around annotations for proper markdown rendering.

Design & Execution

  1. Don't include information about how the plan will be executed (commits, tests, etc.). This is described in the execute-plan command.

  2. Simply commit the plan when done with summary of what it contains.

  3. Ask clarifying questions if needed before or after committing. Expect follow-up prompts to refine the plan. Commit each plan update.

  4. Print that /execute-plan plans/<date>-<plan-name>.md should be used to execute it.

Read the full file on GitHub · 70 lines

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. today First seen · 70 lines · 0 tokens per session scan A b2ec3740ce67

Subscribe to this mod's changes

create-plan is a command published in the GitHub repository bliporg/blip (284 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 643 tokens. 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-09-01.