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/shape-section.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/shape-section)<a href="https://agentmods.dev/commands/buildermethods/design-os/shape-section"><img src="https://agentmods.dev/badge/commands/buildermethods/design-os/shape-section/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/shape-section"><img src="https://agentmods.dev/badge/commands/buildermethods/design-os/shape-section.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.01639 |
| Opus 5.5 | $0.00000 | $0.00656 |
| Sonnet 5.5 | $0.00000 | $0.00328 |
| Haiku 4.5 | $0.00000 | $0.00164 |
Grade A, and why
shape-section 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shape Section
You are helping the user define the specification for a section of their product. This is a conversational process to establish the scope of functionality, user flows, and UI requirements — then automatically generate the spec and sample data.
Step 1: Check Prerequisites
First, verify that /product/product-roadmap.md exists. If it doesn't:
"I don't see a product roadmap defined yet. Please run /product-roadmap first to define your product sections, then come back to shape individual sections."
Stop here if the roadmap doesn't exist.
Step 2: Identify the Target Section
Read /product/product-roadmap.md to get the list of available sections.
If there's only one section, auto-select it. If there are multiple sections, use the AskUserQuestion tool to ask which section the user wants to work on:
"Which section would you like to define the specification for?"
Present the available sections as options.
Step 3: Gather Initial Input
Once the section is identified, invite the user to share any initial thoughts:
"Let's define the scope and requirements for [Section Title].
Do you have any notes or ideas about what this section should include? Share any thoughts about the features, user flows, or UI patterns you're envisioning. If you're not sure yet, we can start with questions."
Wait for their response. The user may provide raw notes or ask to proceed with questions.
Step 4: Ask Clarifying Questions
Use the AskUserQuestion tool to ask 4-6 targeted questions to define:
- Main user actions/tasks - What can users do in this section?
- Information to display - What data and content needs to be shown?
- Key user flows - What are the step-by-step interactions?
- UI patterns - Any specific interactions, layouts, or components needed?
- Scope boundaries - What should be explicitly excluded?
Example questions (adapt based on their input and the section):
- "What are the main actions a user can take in this section?"
- "What information needs to be displayed on the primary view?"
- "Walk me through the main user flow - what happens step by step?"
- "Are there any specific UI patterns you want to use (e.g., tables, cards, modals)?"
- "What's intentionally out of scope for this section?"
- "Are there multiple views needed (e.g., list view and detail view)?"
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 · 169 lines · 0 tokens per session scan A 7e6d8a3b687f
shape-section 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,639 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.
shape-section compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| shape-sectionbuildermethods/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 |