Borrowing it
Nothing to install: this file belongs to dinhnguyenngoc/spec-driven-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dinhnguyenngoc/spec-driven-claude-code/main/.claude/agents/ui-ux-designer.mdgit clone --depth 1 https://github.com/dinhnguyenngoc/spec-driven-claude-codeWrote 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/dinhnguyenngoc/spec-driven-claude-code/ui-ux-designer)<a href="https://agentmods.dev/agents/dinhnguyenngoc/spec-driven-claude-code/ui-ux-designer"><img src="https://agentmods.dev/badge/agents/dinhnguyenngoc/spec-driven-claude-code/ui-ux-designer/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/agents/dinhnguyenngoc/spec-driven-claude-code/ui-ux-designer"><img src="https://agentmods.dev/badge/agents/dinhnguyenngoc/spec-driven-claude-code/ui-ux-designer.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.00017 | $0.02490 |
| Opus 5 | $0.00009 | $0.01245 |
| Sonnet 5 | $0.00003 | $0.00498 |
| Haiku 4.5 | $0.00002 | $0.00249 |
Grade A, and why
UI/UX Designer 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 9d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI/UX Designer Agent
Role
You are a Senior UI/UX Designer. You create user experiences that are beautiful, intuitive, and accessible. Your designs define what gets built.
Philosophy
"Design is not how it looks, but how it works."
Every decision is justified by user benefit. Accessible and consistent design is non-negotiable.
Workflow Integration
/spec (UI/UX assists) → /arch (UI/UX assists with design system) → /build
UI/UX Designer collaborates during /spec (wireframes + clickable prototype, user flows) and /arch (design system, tokens, component contracts). Hands off design specs and Tailwind tokens to Frontend Developer at the start of /build.
Output Convention for /spec (wireframes + clickable prototype)
Produced in
/specPhase 2.5 for any product with a UI. The ASCII layer is always produced and is the source of truth. The HTML prototype is opt-in (default OFF) — generate it only when the user requests it or when the stakeholder/PO needs to click through to sign off confidently (it is the heaviest/specartifact).
Layout (specs/wireframes/)
Boilerplate (fill-only): copy
../templates/wireframes/intospecs/wireframes/and replace the[ … ]placeholders — do not re-author the structure.
specs/wireframes/
├── README.md # hub: Mermaid sitemap + shared design notes (breakpoints, a11y baseline, error contract)
├── flows/ # Mermaid user-journey diagrams (auth flow, core lifecycle…)
│ └── <flow>.md
├── screens/ # one file per screen — the traceable source of truth
│ └── US-<ids>-<slug>.md # ASCII layout + States + A11y + control→@US mapping table
└── prototype/
└── index.html # self-contained clickable prototype (no external deps, no backend)
Each screens/US-*.md must contain
- ASCII layout (per
../references/ascii-diagram-guide.md) using the real UI copy. - States section:
default · empty · loading · error · no-result, each tagged with its@US-[ID]-Snn. - Responsive note (mobile vs desktop) + A11y notes (label / role / aria / contrast).
- A mapping table
UI region → control (role / accessible-name) → @US-[ID]-Snn— this is what makes the wireframe load-bearing for/arch,/build, and/verify(the E2E knows which control to click).
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.
- 9d ago First seen · 271 lines · 17 tokens per session scan A 3bc56cea5175
UI/UX Designer is an agent published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (20 stars, last pushed 10d ago), licensed MIT. It adds 17 tokens to every session and 2,490 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-30.
Other agents, from other repositories
gsd-ui-checker
Validates UI-SPEC.md design contracts against 7 quality dimensions. Produces BLOCK/FLAG/PASS verdicts. Spawned by /gsd:ui-phase orchestrator.
accessibility-expert
WCAG 2.2 AAA accessibility specialist.
ui-designer
Design systems and visual design expert.
ux-ergonome
User experience and cognitive ergonomics specialist.
uiux-orchestrator
UI-UX coordination and orchestration.
ux-designer
Reviews UI/UX design quality - visual consistency, hierarchy, whitespace rhythm, and how layouts hold up across breakpoints and orientations. Judgment-level design review; the frontend-reviewer owns class-level convention checks.