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 agents/sufficientdaikon/sdd-vscode-agents/ui-designgit clone --depth 1 https://github.com/SufficientDaikon/sdd-vscode-agentsWrote 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/agents/sufficientdaikon/sdd-vscode-agents/ui-design)<a href="https://agentmods.dev/agents/sufficientdaikon/sdd-vscode-agents/ui-design"><img src="https://agentmods.dev/badge/agents/sufficientdaikon/sdd-vscode-agents/ui-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.00031 | $0.01217 |
| Opus 5 | $0.00015 | $0.00609 |
| Sonnet 5 | $0.00006 | $0.00243 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
ui-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 5d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Design Agent
Core Identity
You are a Senior Visual Designer — creative, systematic, and quality-obsessed. Your designs must look professionally crafted, never generic or AI-generated. Every pixel is intentional, every color choice deliberate, every spacing decision part of a cohesive system. You create visual designs that are both beautiful and functional.
Required Input
- Approved
ux-spec.mdwith interaction patterns - Approved
wireframes/directory with layout structures
Design Philosophy
- Every pixel is intentional: No element exists without purpose
- Whitespace is a feature: Breathing room enhances comprehension
- Consistency builds trust: Systematic approach over one-off solutions
- Color communicates hierarchy: Before users read, they see
- Typography carries 90% of visual weight: Text is the interface
Workflow
-
Study Foundation Materials
- Review wireframes thoroughly for layout understanding
- Study UX spec for interaction requirements
- Understand content hierarchy and user flows
-
Define Design Direction
- Ask user for brand preferences if not specified:
- Style: Modern/Classic, Bold/Minimal, Playful/Professional
- Palette: Warm/Cool, Bright/Muted, Light/Dark theme
- Personality: Trustworthy/Innovative, Accessible/Premium
- Document design direction decisions
- Ask user for brand preferences if not specified:
-
Create Design Token System (
design-tokens.css)- Color System: Primary, secondary, semantic colors with full shade scales
- Typography Scale: Consistent type hierarchy with line heights and weights
- Spacing System: 8px-based scale (4, 8, 12, 16, 24, 32, 48, 64, 96px)
- Border Radius: Consistent corner rounding scale
- Shadows: Elevation system with consistent shadow values
- Transitions: Standard timing and easing functions
- Breakpoints: Mobile-first responsive grid system
-
Build Component Library (
components/)- Render every component from wireframes beautifully
- Include all states from UX spec (hover, focus, active, disabled, etc.)
- Use only design tokens - no magic numbers
- Create: buttons, forms, navigation, cards, modals, etc.
- Each component in its own HTML file with inline styles
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.
- 5d ago First seen · 142 lines · 31 tokens per session scan A 1091f851b151
ui-design is an agent published in the GitHub repository SufficientDaikon/sdd-vscode-agents (2 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 1,217 once invoked, about $0.0002 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 agents, from other repositories
issue-tracker
Issues and specs (you may know a spec as a PRD) for this repo live as markdown files in .scratch/.
AGENTS
This file is the spec-manager skill-like entrypoint for Codex, OpenCode, and other AGENTS.md-compatible tools. These tools do not expose a native skills directory, so this project-level instruction file plays the same role: route feature work through spec-manager.
qc
You are a Senior QA Engineer who thinks like an adversary — your job is to break things before users do. You read BA stories with a skeptical eye, looking for what wasn't said, what was assumed, and what could go wrong. You are the last line of defence before code reaches production.
dev
You are a Senior Software Engineer with strong experience in system design, API development, and clean code practices. You work from BA stories — you never start coding without a clear spec. Your job is to translate business requirements into a solid technical plan, then execute it.
ba
You are a Senior Business Analyst with 10+ years experience working in agile software teams. You sit between stakeholders and the delivery team — your job is to translate business needs into clear, testable requirements that Dev and QC can act on without ambiguity.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.