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/hainamchung/agent-assistant/designgit clone --depth 1 https://github.com/hainamchung/agent-assistantWrote 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/hainamchung/agent-assistant/design)<a href="https://agentmods.dev/commands/hainamchung/agent-assistant/design"><img src="https://agentmods.dev/badge/commands/hainamchung/agent-assistant/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.00009 | $0.00442 |
| Opus 5 | $0.00005 | $0.00221 |
| Sonnet 5 | $0.00002 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
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 yesterday.
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.
What it actually says
/design — Design Router
ROUTER DIRECTIVE: Analyze design need and route to appropriate workflow.
$ARGUMENTS
🛑 PRE-FLIGHT (DO FIRST — BLOCKS EXECUTION)
LOAD now (in order; path ./rules/ or ~/.{TOOL}/skills/agent-assistant/rules/):
- CORE.md — Identity, Laws, Routing
- PHASES.md — Phase Execution
- AGENTS.md — Tiered Execution
⛔ Do not run any workflow phase until all are loaded. Follow all rules in those files. Then run this file's ROUTING LOGIC, LOAD the chosen variant workflow, and execute it.
ROUTING LOGIC
IF design is simple (component, quick mockup):
→ Route to /design:fast
IF design is complex (full feature, system):
→ Route to /design:hard
IF design is complex AND maximum quality with team collaboration needed:
→ Route to /design:team
IF unsure:
→ Default to /design:fast
AVAILABLE ROUTES
| Route | When to Use |
|---|---|
/design:fast |
Quick component design, simple UI |
/design:hard |
Full feature design, system design |
/design:team |
Maximum quality with parallel agent team collaboration |
PRESENT OPTIONS
## 🎨 Design Mode Selection
**Request**: [parsed request]
**Choose workflow:**
1. ⚡ **Fast** → `/design:fast` — Quick design
2. ⚡⚡⚡ **Hard** → `/design:hard` — Full design process
3. 👥 **Team** → `/design:team` — Full team collaboration (parallel agents, maximum quality)
⏳ Awaiting selection...
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.
- yesterday First seen · 71 lines · 9 tokens per session scan A 7b11082b3e22
design is a command published in the GitHub repository hainamchung/agent-assistant (54 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 442 once invoked, about $0.0000 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-09-03.
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.