Borrowing it
Nothing to install: this file belongs to tomdwipo/claude-soul. 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/tomdwipo/claude-soul/main/.claude/commands/breakdown-design.mdgit clone --depth 1 https://github.com/tomdwipo/claude-soulWrote 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/tomdwipo/claude-soul/breakdown-design)<a href="https://agentmods.dev/commands/tomdwipo/claude-soul/breakdown-design"><img src="https://agentmods.dev/badge/commands/tomdwipo/claude-soul/breakdown-design.svg" alt="Measured on agentmods" 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.04197 |
| Opus 5 | $0.00000 | $0.02099 |
| Sonnet 5 | $0.00000 | $0.00839 |
| Haiku 4.5 | $0.00000 | $0.00420 |
Grade A, and why
breakdown-design 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 8d 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
breakdown-design Command
Create a detailed step-by-step implementation plan for $ARGUMENTS with comprehensive before/after code examples create file at .docs/year(YYYY)/month(MM)/day(DD)/{number-in-DD-folder(01)}-{Feature Spec}/{Feature Spec}-implementation-plan.md if requirement is clear or no have follow up question. think hard and provide a comprehensive implementation plan with before/after code examples for each step. follow YAGNI principle so dont create dead code or unnecessary files. max 29000 characters. If the result exceeds 29000 characters, leave it as is — do NOT truncate, summarize, or drop sections to fit the limit. Completeness of the implementation plan takes precedence over the character cap.
Template Structure
Step-by-Step Implementation Plan with Before/After Code
Provide a breakdown that includes:
- Clear Step Numbering: Each step should be numbered and have a descriptive title
- Before/After Code Blocks: Show exact code changes for each step (add comments for code what you are changing)
- Technical Rationale: Explain why each change is needed
- Dependencies: Note any imports or setup required
- Testing Considerations: How to verify each step works
- Observability logging: Add logging at the appropriate level — see §Observability for the full Decision Guide:
Timber.e(throwable, "…")— errors with a Throwable (records a non-fatal in Crashlytics)Timber.e("…")— errors without a Throwable (breadcrumb + pattern scan)Timber.w("…")— degraded-behaviour paths in real app logic (breadcrumb + pattern scan)Timber.d("…")— diagnostics + monitoring/instrumentation chatter (breadcrumb only)Timber.i("…")— lifecycle / info-level milestones (breadcrumb only) Fall back toLog.d/i/w/e("TAG", "…")if Timber is not on the module classpath.
- Unit Testing: Include unit tests for each step
- Flow Diagram Update: Include an ASCII flow diagram showing the BEFORE and AFTER user/data flow (screen transitions, ViewModel ↔ UseCase ↔ Repository calls, branches, side-effects). Use ASCII box-drawing (
┌─┐ │ └─┘ → ↓ ↑) — no Mermaid, no images. If the change does not alter any flow (pure refactor / cosmetic), writeFlow Diagram: N/A — no flow changeand explain in one line why.
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.
- 8d ago First seen · 335 lines · 0 tokens per session scan A c0c83130c093
breakdown-design is a command published in the GitHub repository tomdwipo/claude-soul (24 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,197 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-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.