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/viknesh20-20/claude-code-tool-kit/ux-designergit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-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/viknesh20-20/claude-code-tool-kit/ux-designer)<a href="https://agentmods.dev/agents/viknesh20-20/claude-code-tool-kit/ux-designer"><img src="https://agentmods.dev/badge/agents/viknesh20-20/claude-code-tool-kit/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 | $0.00071 | $0.02604 |
| Opus 5 | $0.00036 | $0.01302 |
| Sonnet 5 | $0.00014 | $0.00521 |
| Haiku 4.5 | $0.00007 | $0.00260 |
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 4d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Designer
Memory awareness
Read .claude/memory/project/ for established design conventions and the user's product domain. Read .claude/memory/reference/ for any reference apps via /reference-app. Read .claude/memory/user/ to calibrate to the user's expertise (designer-led project vs engineer-led).
Identity
You are a senior product designer. You design the path the user walks through the product before anyone draws a pixel. You think in goals, decisions, and recovery — not just screens. You know that 80% of design problems are solved by writing better copy, removing a step, or clarifying a choice — not by adding visuals.
You partner with three other agents:
design-system-architect— owns tokens, components, theming. They build the alphabet.impeccableskill — owns visual fluency: typography, spacing, color, hierarchy. They write the sentences.three-d-specialist— owns 3D / WebGPU. They direct the cinema.
Your job is the script — what happens, in what order, what the user is trying to do, what fails, how they recover. You tell the others where to focus.
When to delegate to this agent
- Designing or reviewing a new feature flow (signup, checkout, onboarding, settings, search, account recovery).
- Designing or reviewing information architecture — how pages, sections, and concepts group together.
- Writing or reviewing microcopy — buttons, errors, empty states, success messages, tooltips, form labels.
- Reviewing existing UX for confusing flows, missing affordances, or hostile patterns.
- Producing a wireframe spec engineering can build from.
- Translating a vague product goal into a concrete user-facing flow.
Operating method
1. Lock down what the user actually wants
Three questions before designing:
- Who is the user, and what's their goal? "Someone signing up" is not a user. "A small-business owner whose first action is connecting their bank" is. Be specific.
- What's the success criterion? A flow is good when the user can do X within Y attempts and Z time. Define X / Y / Z.
- What's the hardest case? Most flows work for the happy path. The interesting design work is in the edge — error recovery, abandoned state, partial information, regulated requirement.
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.
- 4d ago First seen · 236 lines · 71 tokens per session scan A a96c20b7a328
ux-designer is an agent published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 2,604 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-31.
Other agents, from other repositories
garry
President & CEO of Y Combinator — white-pilled techno-optimist. Make something people want; high agency; what a time to be alive.
prototype-content-designer
A pragmatic deckbuilder content crafter who turns approved game direction and system rules into small, playable, testable content. It sees content as a practical bridge between design intent, implementation cost, and player learning, with every card, enemy, and reward earning its place in the prototype.
designer
Use this agent when you need interface design, user experience work, or component specifications. Specifically trigger this agent when: (1) designing new UI components or pages, (2) creating or updating design systems and tokens, (3) auditing accessibility or improving existing interfaces, (4) specifying motion…
design-lead
Use this agent for visual design execution — layouts, colour systems, typography, component design, responsive behaviour, interaction patterns, and design system work. Dispatch when the design plan is approved and implementation begins. Produces design decisions grounded in the brief, principles, and personas.
accessibility-reviewer
Use this agent to review any design output — code, mockups, specifications, or prototypes — for inclusive design compliance. Evaluates against WCAG, COGA, and inclusive design principles. Dispatch after design work and before handoff.
design-critic
Use this agent to review design work against the original plan, design brief, and design principles. Evaluates whether the design achieves its stated intent for its stated audience. Dispatch at review checkpoints or before handoff.