Borrowing it
Nothing to install: this file belongs to bredmond1019/claude-sdk-rs. 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/bredmond1019/claude-sdk-rs/main/.claude/commands/plan.mdgit clone --depth 1 https://github.com/bredmond1019/claude-sdk-rsWrote 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/bredmond1019/claude-sdk-rs/plan)<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/plan"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/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/bredmond1019/claude-sdk-rs/plan"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/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.05028 |
| Opus 5.5 | $0.00000 | $0.02011 |
| Sonnet 5.5 | $0.00000 | $0.01006 |
| Haiku 4.5 | $0.00000 | $0.00503 |
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 11d 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan — Author an initiative: its narrative and its block records.
Variables
$ARGUMENTS — free-text description of the feature, experiment, or body of work to plan.
Optional flags: --founding, --clarify.
| Flag | What it does |
|---|---|
--founding |
This is the project's founding roadmap — a new repo's first blocks. Adds the Goal / Destination / Architecture framing and writes to planning/founding/. Invoked by /new-project. |
--clarify |
Force the clarify gate on regardless of planning/harness.json. |
--no-redteam |
Skip the adversarial pass (step 10). For a small, low-risk initiative only. |
Purpose
Author one initiative: a coherent body of work in one repo, spanning one or more blocks. Output is two things:
planning/<slug>/plan.md— the authored narrative: the goal, the sequencing rationale, the architecture framing, the cut list. Everything true of the set rather than of any one block.planning/blocks/<BlockID>.json— one block record per block. The definition of each member.
/plan does not write tasks.json. Task decomposition is deferred to
/generate-tasks <BlockID>, run later, per block — because a later block's tasks depend on an
earlier block's code, and decomposing everything at authoring time burns tokens on work that gets
re-derived anyway (D65).
Scope ladder. Multi-repo program →
/generate-roadmap. One repo, multiple blocks → here. A single block →/ticket(behavior change) or/chore(maintenance).master-plan.mdis generated from the block graph, not authored — never hand-write one.Upstream. For work on an existing system large enough that the cut is not obvious, the pre-plan pipeline runs first:
/assess→/seams→/sequence. Its output,planning/<slug>/sequence.md, is this command's authored input (step 3a). Planning a substantial change to an existing subsystem without a seam map produces a cut along architectural layers, which is the failure mode where nothing is usable until the end.
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.
- 11d ago First seen · 364 lines · 0 tokens per session scan A 33fa8c60b0a0
plan is a command published in the GitHub repository bredmond1019/claude-sdk-rs (23 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 5,028 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-10-26.
plan compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| planbredmond1019/claude-sdk-rs | Command | 23 | 1mo ago | Apache-2.0 | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |