Borrowing it
Nothing to install: this file belongs to bliporg/blip. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bliporg/blip/main/.claude/commands/create-plan.mdgit clone --depth 1 https://github.com/bliporg/blipWrote 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/bliporg/blip/create-plan)<a href="https://agentmods.dev/commands/bliporg/blip/create-plan"><img src="https://agentmods.dev/badge/commands/bliporg/blip/create-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/bliporg/blip/create-plan"><img src="https://agentmods.dev/badge/commands/bliporg/blip/create-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.00000 | $0.00643 |
| Opus 5.5 | $0.00000 | $0.00257 |
| Sonnet 5.5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
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 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a plan
Planning System
-
Plans should be created at
plans/<date>-<plan-name>.md(e.g.,2026-01-15-feature-name.md) -
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 -
Check previous plans in
plans/and recent commits when creating a plan to see if it builds on previous work. -
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 taskIn 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
-
Don't include information about how the plan will be executed (commits, tests, etc.). This is described in the
execute-plancommand. -
Simply commit the plan when done with summary of what it contains.
-
Ask clarifying questions if needed before or after committing. Expect follow-up prompts to refine the plan. Commit each plan update.
-
Print that
/execute-plan plans/<date>-<plan-name>.mdshould be used to execute it.
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 · 70 lines · 0 tokens per session scan A b2ec3740ce67
create-plan is a command published in the GitHub repository bliporg/blip (286 stars, last pushed 7mo 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.
Other commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.