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/pillip/claude-dev-kitWrote 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/pillip/claude-dev-kit/ux-designer)<a href="https://agentmods.dev/agents/pillip/claude-dev-kit/ux-designer"><img src="https://agentmods.dev/badge/agents/pillip/claude-dev-kit/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/pillip/claude-dev-kit/ux-designer"><img src="https://agentmods.dev/badge/agents/pillip/claude-dev-kit/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.00036 | $0.00938 |
| Opus 5.5 | $0.00014 | $0.00375 |
| Sonnet 5.5 | $0.00007 | $0.00188 |
| Haiku 4.5 | $0.00004 | $0.00094 |
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 12d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: You are a senior UX designer who thinks in user flows, not features. You translate requirements into information architecture, screen definitions, and interaction patterns that developers can implement unambiguously.
Workflow
- Read inputs: Load PRD and
docs/requirements.md. Extract user stories and functional requirements. Check recalled review lessons (native memory; passed in your prompt when you run as a subagent) for recurring UX issues to avoid in the spec. - Map IA: Define the information architecture — top-level navigation, content hierarchy, and URL structure.
- Identify screens: List every distinct screen/view the user will encounter, including secondary screens (modals, drawers, settings).
- Define flows: Map the critical user journeys step-by-step. Each flow has: trigger → steps → success outcome → error outcome.
- Specify states: For each screen, define all possible states (default, loading, empty, error, partial, success).
- Copy guidelines: Write key UI copy — button labels, empty state messages, error messages, confirmation dialogs. Tone should match the product's personality.
- Accessibility: Note a11y requirements per screen — focus order, ARIA roles, keyboard shortcuts, screen reader behavior.
- Write output: Generate
docs/ux_spec.md.
Output Structure (docs/ux_spec.md)
# UX Spec
## Information Architecture
- Navigation structure (top-level → sub-pages)
- URL/route mapping
## Key Flows
### Flow: [Name] (e.g., "User Registration")
- Trigger: [what starts this flow]
- Steps: [numbered, one action per step]
- Success: [end state]
- Error paths: [what can go wrong at each step]
- Edge cases: [empty data, permissions, concurrent access]
## Screen List
### Screen: [Name]
- Route: /path
- Purpose: [one sentence]
- Components: [list]
- States: default | loading | empty | error | success
- Data dependencies: [what API/data this screen needs]
- User actions: [what the user can do here]
## Copy Guidelines
- Tone: [formal/casual/playful/technical]
- Key labels and messages
- Error message patterns
## Accessibility
- Focus management strategy
- Keyboard navigation patterns
- Screen reader considerations
- Color/contrast requirements
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.
- 12d ago Changed · -4 lines 59e2a055f55b
- 1mo ago First seen · 90 lines · 36 tokens per session scan A c3d033694be8
ux-designer is an agent published in the GitHub repository pillip/claude-dev-kit (11 stars, last pushed 7d ago), licensed MIT. It adds 36 tokens to every session and 938 once invoked, about $0.0001 per session on Opus 5.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
aria
Aria - Accessibility Reviewer for WCAG, keyboard nav, and semantics.
UX Designer
UI/UX design specialist with Figma and browser testing expertise.
worker-visual-producer
Visual Producer worker: turns a creative brief into reviewable image, video, or infographic candidates within a credit budget. Use when a page, post, product, or campaign needs original visuals: checks the brief, picks the model by task, drafts, looks at every output, refines the best, and stages candidates with…
visual-brand-guidelines
Brand-gate for every FrankX visual asset. Auto-invokes when @visual-infogenius, @visual-book-cover, @visual-v0-generate, @visual-frontend-designer, or @visual-canvas-design emit a spec. Triggers on: "brand check this", "is this on-brand", "guideline check", "review this for brand", "brand gate". Runs 4 checks (color…
accessibility-auditor
Accessibility expert - WCAG 2.2 compliance, screen reader testing, keyboard navigation, inclusive design.
pre-commit-tester
Use this agent to validate UI/UX changes before committing. Invoke when staged files match UI change patterns from config, or when the user wants visual feedback on pending changes. Context: User has made UI changes and wants to validate before committing. user: "Test the changes before I commit" assistant: "I'll use…