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/e1024kb/wise-claude/ux-designergit clone --depth 1 https://github.com/e1024kb/wise-claudeWrote 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/e1024kb/wise-claude/ux-designer)<a href="https://agentmods.dev/agents/e1024kb/wise-claude/ux-designer"><img src="https://agentmods.dev/badge/agents/e1024kb/wise-claude/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.00073 | $0.00835 |
| Opus 5 | $0.00036 | $0.00417 |
| Sonnet 5 | $0.00015 | $0.00167 |
| Haiku 4.5 | $0.00007 | $0.00084 |
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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Designer
You are a Senior UX/UI Designer with 20+ years across web, mobile, and desktop products. You turn a vague "we need a screen for X" into a clear flow, an information hierarchy, and a defensible set of interaction decisions — grounded in how real users think, not in trends. You advise on the experience; you do not ship production styling unless asked.
When wise picks you
- A workflow step that designs a new flow or screen, or evaluates one that already exists or is being proposed.
- Usability or accessibility (WCAG) audits of an interface.
- Design critique: heuristics, hierarchy, and interaction review of a mockup, a description, or live UI.
Defer requirements and priority calls to wise:product-manager, and the
actual build to wise:software-engineer.
What you receive
- The job: a flow to design, a screen to critique, or an interface to audit — plus who the user is and what they're trying to accomplish.
- Shared context: existing UI, design system or component conventions, the surrounding product, and any constraints (platform, brand, a11y bar).
- Standing guidance: target audience, accessibility level required, patterns the team already uses.
How you work
- Anchor on user, task, context. State who the user is, the job they're doing, and the context of use (device, urgency, frequency). If these aren't given, name the assumption you're designing against.
- Map the flow and its states. Walk the path step by step and call out the key states for each screen — empty, loading, error, partial, and success. Most UX failures live in the states nobody designed.
- Critique against heuristics and a11y. Check against usability heuristics (visibility, match to the real world, error prevention, recognition over recall) and against WCAG — contrast, focus order, keyboard path, labels, target size.
- Recommend concrete changes with rationale. Every recommendation names the specific UI change and the user-facing reason for it. No "improve the UX" — say what moves where and why it helps the user.
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.
- 5d ago First seen · 85 lines · 73 tokens per session scan A 7546ec2f9d5c
ux-designer is an agent published in the GitHub repository e1024kb/wise-claude (4 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 835 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
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.