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.
git clone --depth 1 https://github.com/superbenefit/sb-marketplaceWrote 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/superbenefit/sb-marketplace/design)<a href="https://agentmods.dev/commands/superbenefit/sb-marketplace/design"><img src="https://agentmods.dev/badge/commands/superbenefit/sb-marketplace/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.00020 | $0.01948 |
| Opus 5 | $0.00010 | $0.00974 |
| Sonnet 5 | $0.00004 | $0.00390 |
| Haiku 4.5 | $0.00002 | $0.00195 |
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 7d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design Command
Architecture planning and system design for complex Astro and Starlight projects. Provides structured design documents, schemas, and implementation roadmaps.
Usage
/design [architecture or system description]
Description
The /design command helps you plan complex system architectures before implementation. It loads architecture patterns from the astro-coding skill and creates comprehensive design documents with schemas, routing strategies, and implementation roadmaps.
Note: This command focuses on planning and documentation only. Use /dev to implement the designs.
What It Does
- Analyzes Requirements: Understands your system needs and constraints
- Designs Architecture: Creates collection structures, routing strategies, data flow
- Provides Schemas: Defines TypeScript schemas and data models
- Plans Implementation: Creates step-by-step implementation roadmap
- Documents Decisions: Explains architectural choices and trade-offs
When to Use
Use /design when you need:
- Complex content architecture for multi-collection systems
- Multi-source content strategy (API + local files + external CMS)
- Custom loader architecture planning
- Integration strategies for external services
- Refactoring guidance for existing systems
- Team documentation for complex features
Don't use for simple components or standard features - just use /dev directly.
Examples
Content Collections Design
/design Blog system with categories, tags, authors, and related posts
Output: Collection schemas, relationship structures, query patterns, implementation steps
Multi-Source Content
/design System that combines local MDX, GitBook API content, and PostgreSQL data
Output: Loader architecture, data transformation patterns, caching strategies, integration approach
Complex Routing
/design Multi-language documentation with versioning and fallbacks
Output: Route structure, content organization, i18n strategy, implementation roadmap
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.
- 7d ago First seen · 318 lines · 20 tokens per session scan A fbbaf6d37fd4
design is a command published in the GitHub repository superbenefit/sb-marketplace (5 stars, last pushed 7mo ago), licensed CC0-1.0. It adds 20 tokens to every session and 1,948 once invoked, about $0.0001 per session on Opus 5. 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-31.
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.