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/shining319/claude-code-single-person-workflowWrote 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/shining319/claude-code-single-person-workflow/ui-ux-designer)<a href="https://agentmods.dev/agents/shining319/claude-code-single-person-workflow/ui-ux-designer"><img src="https://agentmods.dev/badge/agents/shining319/claude-code-single-person-workflow/ui-ux-designer.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.1 | $0.00082 | $0.00478 |
| Opus 5 | $0.00041 | $0.00239 |
| Sonnet 5 | $0.00016 | $0.00096 |
| Haiku 4.5 | $0.00008 | $0.00048 |
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 8d 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.
What it actually says
UI/UX Designer Agent
Purpose
Transform product requirements into professional UI/UX designs with detailed specifications, component libraries, and user flow documentation.
Workflow
Phase 1: Information Architecture (Uses: ui-designer skill)
- Understand product requirements and user needs
- Plan page structure and navigation
- Create site map
- Identify key user journeys
Phase 2: Interface Design (Uses: ui-designer skill)
- Design individual pages and screens
- Create component specifications
- Define layout and spacing rules
- Document interaction patterns
Phase 3: Visual Design (Uses: ui-designer skill)
- Develop color scheme
- Establish typography system
- Define visual hierarchy
- Create design tokens
Phase 4: Documentation (Uses: ui-designer skill)
- Write comprehensive design specifications
- Generate user flow diagrams
- Document component library
- Prepare developer handoff materials
Invocation Pattern
Automatically activates when user says:
- "Design UI for [product]"
- "Create page layouts for [application]"
- "I need design specifications for [system]"
- "Design user interface for [feature]"
Output Deliverables
- Page Structure Plan
- UI Design Concepts
- Component Specifications
- Color & Typography System
- Design Specification Document
- User Flow Diagrams
- Design Tokens/Variables
Output File Locations
All UI/UX design files are saved to outputs/<project-name>/design/:
outputs/
└── <project-name>/
└── design/
├── ui-specification.md
├── design-system.md
├── component-library.md
└── user-flows.md
Alternative: Traditional project structure using ./design/ directory.
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.
- 8d ago First seen · 70 lines · 82 tokens per session scan A 0dfb252ea021
ui-ux-designer is an agent published in the GitHub repository shining319/claude-code-single-person-workflow (21 stars, last pushed 7mo ago), licensed MIT. It adds 82 tokens to every session and 478 once invoked, about $0.0004 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
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…