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/generate-master-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/generate-master-plan)<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/generate-master-plan"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/generate-master-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/generate-master-plan"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/generate-master-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.00666 |
| Opus 5.5 | $0.00000 | $0.00266 |
| Sonnet 5.5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
generate-master-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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Master Plan — superseded by /plan --founding (D65)
This command no longer authors anything
master-plan.md is generated from the block graph (planning/blocks/*.json +
planning/state.json), not authored by hand. Writing one by hand is how it became sediment: 15
live copies across the fleet, three over 2400 lines, edited mostly by bookkeeping rather than by
anyone planning work.
Use instead:
| You want to | Run |
|---|---|
| Plan a new project's founding roadmap | /plan --founding |
| Plan an initiative in one repo (any number of blocks) | /plan |
| Plan work spanning several repos | /generate-roadmap |
| Plan a single behavior change | /ticket |
| Plan a single maintenance task | /chore |
Why this changed
Governed by D65.
The block record at planning/blocks/<BlockID>.json is now the authored definition of a block —
its what, why, files, out-of-scope, interfaces, and acceptance criteria. /generate-tasks reads
that record. The markdown roadmap is a view over the block graph, and a view can be regenerated
rather than maintained.
What the narrative layer still holds — the goal, the destination, the architecture framing, the
sequencing rationale, the cut list — is genuinely about the set rather than any one block, and
lives in an initiative's planning/<slug>/plan.md, authored by /plan.
/plan --founding is the same code path as /plan, with the founding framing sections and a
planning/founding/ destination. There is no separate founding format.
If you are looking for the old behavior
- The block skeleton (What / Why / SDLC workflow / Model / Files / Interfaces / Out of scope /
Depends on / Acceptance criteria) is now the block record's field contract:
.claude/workflows/block.schema.json. - The registration steps (block ID,
state.jsoncreation and registration, the cross-repo edge prompt,mev emit-state --write) are.claude/workflows/block-registration.md— one copy, shared by every producer. Four drifted copies existed before D65; only one of them created a missingstate.json, which is how at least one repo's block graph went dark. - The wave-table sentinel is unchanged:
mev emit-state --writefills<!-- BEGIN generated:wave-table -->. A file missing the sentinel pair is silently skipped (W_EMIT_NO_SENTINEL).
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 · 54 lines · 0 tokens per session scan A 28c96669f960
generate-master-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 666 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.
generate-master-plan compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| generate-master-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 |