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/educlopez/ui-craftWrote 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/educlopez/ui-craft/sddesign)<a href="https://agentmods.dev/commands/educlopez/ui-craft/sddesign"><img src="https://agentmods.dev/badge/commands/educlopez/ui-craft/sddesign/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/educlopez/ui-craft/sddesign"><img src="https://agentmods.dev/badge/commands/educlopez/ui-craft/sddesign.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.00046 | $0.01367 |
| Opus 5.5 | $0.00018 | $0.00547 |
| Sonnet 5.5 | $0.00009 | $0.00273 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
sddesign 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 1mo 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the spec-driven design pipeline for $ARGUMENTS. Load the ui-craft skill.
ORCHESTRATE-ONLY RULE
This command sequences existing phase commands. It MUST NOT re-implement or duplicate any logic from them. Every composition rule, wireframe algorithm, craft rule, and convergence engine lives in the phase commands. This command contributes only:
- Gate detection (does the artifact exist?)
- Offer prompts (run phase X or skip?)
- Progress reporting (the checklist)
- Degraded-mode honesty (what was skipped and what that costs)
When in doubt: call the phase command, don't inline its steps.
Progress Checklist
Print this at the start and update it after each gate resolves:
[ ] brief [ ] tokens [ ] shape (spec) [ ] craft (build) [ ] converge [ ] ship
Use [✓] for completed/skipped-with-artifact, [>] for the current gate, [–] for skipped-without-artifact (degraded).
Pipeline Gates
Gate 1 — Brief
Check: does .ui-craft/brief.md exist?
If yes: mark [✓] brief. Note that brief §6 learned constraints and the a11y/correctness floor are in effect for all downstream gates — they take precedence over any spec.md composition choice.
If no: offer to run /brief now.
- User confirms → run
/brief. When it completes, mark[✓] brief. - User declines → mark
[–] brief. Note downstream impact: "no brief → craft will use skill defaults; composition will not be anchored to project principles."
Gate 2 — Tokens
Check: does a token spine exist? (Look for CSS variables --color-*, --font-*, --accent-*, a Tailwind theme.extend with tokens, or a token file.)
If yes: mark [✓] tokens.
If no: offer to run /tokens now.
- User confirms → run
/tokens. When it completes, mark[✓] tokens. - User declines → mark
[–] tokens. Note downstream impact: "no token spine → craft will establish a minimal inline token set; it won't match an existing system."
Gate 3 — Shape (spec)
Existing-surface guard: Before running /shape, check if .ui-craft/spec.md already contains a ## Surface: <name> block for this surface. If it does, do NOT re-run shape and blindly append a duplicate section — offer to update the existing section or skip shape (the spec already exists).
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.
- 1mo ago First seen · 108 lines · 46 tokens per session scan A 1220206a0af3
sddesign is a command published in the GitHub repository educlopez/ui-craft (390 stars, last pushed 5d ago), licensed MIT. It adds 46 tokens to every session and 1,367 once invoked, about $0.0002 per session on Opus 5.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-30.
Other commands, from other repositories
style
Apply styling to a component using the project's design system and styling approach.
summary
Generate a consolidated project brief from design artifacts. For the full spec package with YAML specs and validation, use /compile instead.
start-design-plan
Start collaborative design process with brainstorming and planning.
new-feature
Start a complete feature development process from problem framing to DOD and wireframe.
design-research
Research existing design patterns, component inventory, and open UX decisions before starting a new feature design.
checklist
Generate a custom checklist for the current feature based on user requirements.