Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/superclaude-org/superclaude_plugin/sc-designgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_PluginWrote 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/superclaude-org/superclaude_plugin/sc-design)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-design"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-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 | $0.00014 | $0.00691 |
| Opus 5 | $0.00007 | $0.00345 |
| Sonnet 5 | $0.00003 | $0.00138 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
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 4d 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.
This is a copy
92% identical to design — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:sc:sc:design - System and Component Design
Triggers
- Architecture planning and system design requests
- API specification and interface design needs
- Component design and technical specification requirements
- Database schema and data model design requests
Usage
/sc:sc:design [target] [--type architecture|api|component|database] [--format diagram|spec|code]
Behavioral Flow
- Analyze: Examine target requirements and existing system context
- Plan: Define design approach and structure based on type and format
- Design: Create comprehensive specifications with industry best practices
- Validate: Ensure design meets requirements and maintainability standards
- Document: Generate clear design documentation with diagrams and specifications
Key behaviors:
- Requirements-driven design approach with scalability considerations
- Industry best practices integration for maintainable solutions
- Multi-format output (diagrams, specifications, code) based on needs
- Validation against existing system architecture and constraints
Tool Coordination
- Read: Requirements analysis and existing system examination
- Grep/Glob: Pattern analysis and system structure investigation
- Write: Design documentation and specification generation
- Bash: External design tool integration when needed
Key Patterns
- Architecture Design: Requirements → system structure → scalability planning
- API Design: Interface specification → RESTful/GraphQL patterns → documentation
- Component Design: Functional requirements → interface design → implementation guidance
- Database Design: Data requirements → schema design → relationship modeling
Examples
System Architecture Design
/sc:sc:design user-management-system --type architecture --format diagram
# Creates comprehensive system architecture with component relationships
# Includes scalability considerations and best practices
API Specification Design
/sc:sc:design payment-api --type api --format spec
# Generates detailed API specification with endpoints and data models
# Follows RESTful design principles and industry standards
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.
- 4d ago First seen · 96 lines · 14 tokens per session scan A fdbad6a1ed96
design is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 14d ago), licensed MIT. It adds 14 tokens to every session and 691 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to design, differing in 22 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
sc:recommend
Ultra-intelligent command recommendation engine - recommends the most suitable SuperClaude commands for any user input.
analyze
Comprehensive code analysis across quality, security, performance, and architecture domains.
build
Build, compile, and package projects with intelligent error handling and optimization.
design
Design system architecture, APIs, and component interfaces with comprehensive specifications.
document
Generate focused documentation for components, functions, APIs, and features.