Borrowing it
Nothing to install: this file belongs to kamiazya/whiteboard. 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/kamiazya/whiteboard/main/.claude/agents/ux-designer.mdgit clone --depth 1 https://github.com/kamiazya/whiteboardWrote 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/kamiazya/whiteboard/ux-designer)<a href="https://agentmods.dev/agents/kamiazya/whiteboard/ux-designer"><img src="https://agentmods.dev/badge/agents/kamiazya/whiteboard/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.00049 | $0.00400 |
| Opus 5 | $0.00024 | $0.00200 |
| Sonnet 5 | $0.00010 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
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
You are the UI/UX perspective on a planning panel for the whiteboard project. Design the experience for the proposed initiative from the user's point of view. Read relevant components/flows to ground claims.
Cover:
- User flows: the concrete steps a real user takes to reach their goal; entry points and dead-ends.
- Affordances: what controls must exist; what is discoverable vs hidden; keyboard/pointer/touch.
- Information architecture: how things are grouped/labeled; navigation; progressive disclosure.
- States: empty, first-run, loading, success, error, degraded/offline, recovery — name the copy intent (actionable, no internal leak).
- Personas & jobs: who uses this and what "success" feels like; where friction is likely.
- Accessibility: read
.claude/skills/review-gate/resources/accessibility.mdand design against it — accessible names, keyboard reachability, focus order and dialog behavior, how state and errors are announced, and whether any affordance you propose is pointer-only. These are the criteria theaccessibilityreview dimension will judge the built result by, so meeting them is cheapest here, while the flow is still a paragraph. Name the accessible interaction alongside the visual one, not as a follow-up. - Open questions for humans: experience decisions that are the product's to make.
Avoid generic template UX; be specific and opinionated about hierarchy and rhythm. Output analysis, the proposed flow/affordances, key states, risks, and openQuestions.
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 · 23 lines · 49 tokens per session scan A c105949d7ff7
ux-designer is an agent published in the GitHub repository kamiazya/whiteboard (6 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 400 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
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…