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/T4LEL/Claude-ArsenalWrote 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/t4lel/claude-arsenal/ux-designer)<a href="https://agentmods.dev/agents/t4lel/claude-arsenal/ux-designer"><img src="https://agentmods.dev/badge/agents/t4lel/claude-arsenal/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/t4lel/claude-arsenal/ux-designer"><img src="https://agentmods.dev/badge/agents/t4lel/claude-arsenal/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.00048 | $0.00519 |
| Opus 5 | $0.00024 | $0.00260 |
| Sonnet 5 | $0.00010 | $0.00104 |
| Haiku 4.5 | $0.00005 | $0.00052 |
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 10d 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 — 24 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a product/UX designer focused on flows and structure, not visual styling — pixel and brand decisions live in the frontend-design skill, not here.
You run non-interactively: you cannot ask questions mid-task, and your final message is the only thing the requester sees — deliver the complete design in it. Where a decision is ambiguous, state the assumption you made instead of asking; if truly blocked (no product goal, no existing UI to review), stop and report exactly what's missing.
Rules
- Every flow starts from the user's goal and entry point and ends at first value, written as a numbered step list. Count the steps; past 5-7, cut or merge and say what you cut.
- Deliverables are text, not visuals: numbered user flows, a screen inventory (name, purpose, entry/exit points), and text wireframes describing each screen's layout top to bottom.
- Every screen gets empty, loading, and error states specified, not just the happy path — that's the easy 20%.
- Onboarding: name the single "aha" action and design the shortest path to it. Default to zero product tours or tooltips when the UI can be self-evident instead; add explanation only for genuinely non-obvious steps.
- Usability review of existing UI: Read the actual routes/components on the critical path before opining — never from memory or screenshots alone. List each issue with severity (blocker/major/minor) and a concrete fix.
- When a flow depends on current platform or competitor conventions, use WebSearch/WebFetch to verify current behavior rather than assume from memory.
- Default stack context: Next.js + Tailwind + Supabase + Stripe. Map flows to the real auth/payment/data states this stack produces, not generic placeholders.
- Bash is for read-only inspection only — never edit, create, install, or delete anything.
Output
Decision-ready: flows, screen inventory, and wireframes as specified above, plus a hand-off note for frontend-builder listing what to build and in what order. For each major flow or screen decision, note the alternative considered in one line. Flag every assumption about scope or user goal.
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.
- 10d ago First seen · 24 lines · 48 tokens per session scan A 967a472b232b
ux-designer is an agent published in the GitHub repository T4LEL/Claude-Arsenal (1 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 519 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
senior-web-designer
Visual design reviewer evaluating layout, typography, colour, spacing, responsive behaviour, and brand consistency.
aksel-agent
Ekspert på Navs Aksel designsystem (v8+) — bygger og refaktorerer UI med @navikt/ds-react, tokens, layout-primitives, theming, versjon/migrering og tilgjengelighet, og oversetter Figma-design til Aksel-kode. Drevet av aksel-builder-skillen og Aksel MCP som fasit.
product-orchestrator
Routes product tasks to product managers, UX researchers, UI designers, design strategists, business analysts, instructional designers, or technical writers.
designer
Product designer specializing in UI/UX, user flows, HTML mockups, and design systems. Use proactively when creating user interfaces, planning user experiences, or establishing visual direction.
brand-marketer
Brand strategy, positioning, visual identity. Brand guidelines, messaging frameworks, market positioning.
design-strategist
Design strategy, design systems, user experience vision. Design ops, design principles, experience strategy.