Design OS is a product-planning and interface-design tool that guides an idea through product definition, data modeling, design-system choices, screen design, and implementation handoff. Teams use it to give coding agents a clear specification before development begins. Its catalogue add-ons support the guided planning and design workflow.
Borrowing it
Nothing to install: this file belongs to buildermethods/design-os. 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/buildermethods/design-os/main/.claude/commands/design-os/design-tokens.mdgit clone --depth 1 https://github.com/buildermethods/design-osWrote 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/buildermethods/design-os/design-tokens)<a href="https://agentmods.dev/commands/buildermethods/design-os/design-tokens"><img src="https://agentmods.dev/badge/commands/buildermethods/design-os/design-tokens/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/buildermethods/design-os/design-tokens"><img src="https://agentmods.dev/badge/commands/buildermethods/design-os/design-tokens.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.01269 |
| Opus 5.5 | $0.00000 | $0.00508 |
| Sonnet 5.5 | $0.00000 | $0.00254 |
| Haiku 4.5 | $0.00000 | $0.00127 |
Grade A, and why
design-tokens 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Tokens
You are helping the user choose colors and typography for their product. These design tokens will be used consistently across all screen designs and the application shell.
Step 1: Check Prerequisites
First, verify that the product overview exists:
Read /product/product-overview.md to understand what the product is.
If it doesn't exist:
"Before defining your design system, you'll need to establish your product vision. Please run /product-vision first."
Stop here if the prerequisite is missing.
Step 2: Explain the Process
"Let's define the visual identity for [Product Name].
I'll help you choose:
- Colors — A primary accent, secondary accent, and neutral palette
- Typography — Fonts for headings, body text, and code
These will be applied consistently across all your screen designs and the application shell.
Do you have any existing brand colors or fonts in mind, or would you like suggestions?"
Wait for their response.
Step 3: Choose Colors
Help the user select from Tailwind's built-in color palette. Present options based on their product type:
"For colors, we'll pick from Tailwind's palette so they work seamlessly with your screen designs.
Primary color (main accent, buttons, links):
Common choices: blue, indigo, violet, emerald, teal, amber, rose, lime
Secondary color (complementary accent, tags, highlights): Should complement your primary — often a different hue or a neutral variation
Neutral color (backgrounds, text, borders):
Options: slate (cool gray), gray (pure gray), zinc (slightly warm), neutral, stone (warm gray)
Based on [Product Name], I'd suggest:
- Primary: [suggestion] — [why it fits]
- Secondary: [suggestion] — [why it complements]
- Neutral: [suggestion] — [why it works]
What feels right for your product?"
Use AskUserQuestion to gather their preferences if they're unsure:
- "What vibe are you going for? Professional, playful, modern, minimal?"
- "Any colors you definitely want to avoid?"
- "Light mode, dark mode, or both?"
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 · 167 lines · 0 tokens per session scan A 9cf883695f83
design-tokens is a command published in the GitHub repository buildermethods/design-os (1,876 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,269 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.
design-tokens compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| design-tokensbuildermethods/design-os | Command | 1.9k | 1mo ago | MIT | A | 0 | Claude Code |
| profilecathrynlavery/diagram-design | Command | 65k | 3d ago | MIT | A | 16 | Claude Code |
| erne-animateJubaKitiashvili/everything-react-native-expo | Command | 50 | 29d ago | MIT | A | 21 | Claude Code |
| ui-flow-reviewMRCalderon3D/everything-game-dev-code | Command | 104 | 28d ago | MIT | A | 15 | Claude Code |
| responsive-design-specialistimsaif/design-with-claude | Command | 11 | yesterday | MIT | A | 36 | Claude Code |
| design-auditw2ur/claude-code-setup | Command | 2 | 3d ago | MIT | A | 30 | Claude Code |
| ppt-image2-editable-rebuildwwe-dog/ppt-image2-editable-rebuild | Command | 204 | 5mo ago | Unlicense | A | 15 | Claude Code |