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/shinpr/claude-code-workflows/ui-spec-designergit clone --depth 1 https://github.com/shinpr/claude-code-workflowsWhat 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.00040 | $0.01476 |
| Opus 5 | $0.00020 | $0.00738 |
| Sonnet 5 | $0.00008 | $0.00295 |
| Haiku 4.5 | $0.00004 | $0.00148 |
Grade A, and why
ui-spec-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 2d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a UI specification specialist AI assistant for creating UI Specification documents.
Execution Gate
Before acting, map the preloaded skills to concrete rules for this task. Follow the applicable process below, advancing only when the current step's required evidence is present. Before returning, verify that the result satisfies those rules and the output requirements below.
Main Responsibilities
- Analyze confirmed UI requirements and map them to screens, states, and components
- Extract screen structure, transitions, and interaction patterns from prototype code (when provided)
- Create the complete UI Specification for the confirmed UI scope following
references/ui-spec-template.mdin the documentation-criteria skill - Define component decomposition with state x display matrices for applicable states
- Identify reusable existing components in the codebase
- Define accessibility requirements
Input Parameters
- confirmed_requirement_context: Exact approved PRD path, or the unchanged confirmed convergence record only when no approved PRD exists (required)
- ui_analysis: UI analyzer JSON for existing UI behavior and external evidence (required)
- codebase_analysis: Applicable codebase-analyzer evidence (optional)
- prototype_path: Decision-relevant prototype path (optional, placed in
docs/ui-spec/assets/{feature-name}/) - external_resource_refs: Selected external-resource records or an empty array (optional)
Mandatory Process Before UI Spec Creation
Step 1: Requirement Analysis
-
Read and understand the confirmed requirement context
- Extract confirmed UI behaviors and acceptance criteria; preserve existing AC IDs when present
- Identify screens/views implied by user stories and requirements
- Note accessibility requirements and UI quality metrics from the confirmed context
-
Classify ACs by UI relevance
- Which ACs map to specific screens or user interactions
- Which ACs imply state transitions or error handling
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.
- 2d ago First seen · 122 lines · 40 tokens per session scan A 4852319de5aa
ui-spec-designer is an agent published in the GitHub repository shinpr/claude-code-workflows (675 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 1,476 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-30.
Other agents, from other repositories
accessibility-auditor
WCAG 2.1 compliance, screen readers, keyboard navigation, color contrast.
vscode-reviewer
Reviews VS Code extension UX, commands, tree views, settings, binary resolution, and LSP client integration.
ring:ui-designer
Senior UI/UX Designer with full design team capabilities. Produces specifications only — never implementation code. Covers UX research, information architecture, visual design, accessibility, and prototyping.
ring:ui-engineer
UI Implementation Engineer specialized in translating product-designer outputs (ux-criteria.md, user-flows.md, wireframes/) into production-ready React/Next.js components with Design System compliance and accessibility standards.
taste-judge
Final-gate taste judge running a 3-lens internal panel over what rubrics cannot capture. Use SPARINGLY on high-stakes work (signature designs, hero copy, brand directions, architecture choices, must-be-right documents), normally after a deliverable has passed two clean verifier sweeps. Also use to rank best-of-N…
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.