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/system-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/system-design)<a href="https://agentmods.dev/commands/tomdwipo/claude-soul/system-design"><img src="https://agentmods.dev/badge/commands/tomdwipo/claude-soul/system-design/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/tomdwipo/claude-soul/system-design"><img src="https://agentmods.dev/badge/commands/tomdwipo/claude-soul/system-design.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.01890 |
| Opus 5.5 | $0.00000 | $0.00756 |
| Sonnet 5.5 | $0.00000 | $0.00378 |
| Haiku 4.5 | $0.00000 | $0.00189 |
Grade A, and why
system-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 2mo 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
system-design Command
Produce a detailed system design for $ARGUMENTS using ASCII diagrams only (no Mermaid, no
images — per workspace CLAUDE.md), with BEFORE/AFTER so the change is obvious. This is the
architecture artifact ("what it is shaped like + why"), the upstream input to /breakdown-design
(which turns it into step-by-step code). Keep them paired: same feature, same folder.
think hard. Ground every claim in the actual codebase (read the files first — see §Lookup First). follow YAGNI — design only what the goal needs; no speculative components or dead structure.
Output mode — ASK FIRST (this is the whole point of this command)
Parse $ARGUMENTS for an explicit mode flag:
--chat(or the wordchat) → render the full design in chat only, write no file.--file(or the wordfile/md) → write the design to a markdown file (see §File Location), then post a short summary in chat + the handoff line.
If no mode flag is present, ask the user ONCE with AskUserQuestion:
"Where should the system design go?" — options: Chat only / Save to .md file (ready for /breakdown-design).
Do not proceed until the mode is known. Everything else (the design itself) is identical in both modes — only the destination differs.
File Location (when mode = file)
Mirror /breakdown-design exactly so the two artifacts sit side by side in one feature folder:
.docs/YYYY/MM/DD/{NN}-{Feature-Spec}/{Feature-Spec}-system-design.md
YYYY/MM/DD= today (from the session date).{NN}= next free 2-digit number in that day's folder (e.g. existing up to13-…→ use14). Reuse the SAME{NN}-{Feature-Spec}folder if it already exists for this feature, so the later{Feature-Spec}-implementation-plan.mdfrom/breakdown-designlands in the same folder.{Feature-Spec}= short Title-Case-Hyphenated name you infer from $ARGUMENTS.- After writing, print the path + a one-line handoff:
Next: /breakdown-design <feature>so the user can generate the implementation plan from this design.
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.
- 2mo ago First seen · 138 lines · 0 tokens per session scan A 0f9da09391ec
system-design is a command published in the GitHub repository tomdwipo/claude-soul (24 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,890 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.
system-design compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| system-designtomdwipo/claude-soul | Command | 24 | 2mo ago | MIT | 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 |