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 skills add mthines/agent-skills --skill uxgit clone --depth 1 https://github.com/mthines/agent-skillsWrote 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/skills/mthines/agent-skills/ux)<a href="https://agentmods.dev/skills/mthines/agent-skills/ux"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/ux/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/skills/mthines/agent-skills/ux"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/ux.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00090 | $0.01485 |
| Opus 5.5 | $0.00036 | $0.00594 |
| Sonnet 5.5 | $0.00018 | $0.00297 |
| Haiku 4.5 | $0.00009 | $0.00148 |
Grade A, and why
ux 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 2d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX
Audit or plan a UI the way a product reviewer does: start from what the user is trying to get done, prove what the code does, then add accessibility depth. Read every target file completely before reporting on it.
Modes
| Request | Mode | Order of work |
|---|---|---|
"review / audit this page", "ux feedback", /ux (default) |
audit |
Pass 1 → Pass 2 → Verify → Report |
| "plan the X flow", "design the onboarding", "how should X work" | plan |
Flow plan first, then a Pass 1 + Pass 2 audit of any existing code the flow touches |
| "check accessibility", "is this accessible", "check contrast" | a11y |
Pass 1 steps 1–2 only (job + task), then Pass 2 in full |
| "improve copy", "review microcopy" | copy |
rules/ux-writing.md on every user-facing string, ordered by where it sits on the user's path |
| Consent, cancellation, paywall, sign-up, permission prompt, AI chat — in any mode | dark-patterns |
Always also apply rules/dark-patterns.md; any hit is Critical |
Step 0 — Scope
- Resolve the target: the user's named files, else the changed UI files (
git diff --name-only <base>...HEAD), else the current file. - Detect the platform: web (
<div>, CSS, Tailwind), React Native (View,Pressable,expo-router), or both. Ask when ambiguous. - Read the target files, then the handlers, hooks, stores, routes, and API calls they reach — Pass 1 depends on them.
Pass 1 — The user's path (first, always)
Outcome-changing findings (a broken flow, a control that does the wrong thing, a dead end) come from this pass, not from the checklist.
Follow rules/user-path.md:
- Name the page's job and the primary user task in one sentence each.
- Walk the task end to end in the code, from entry to the next step after success.
- For each control on the path, read its handler and state changes, and compare what it does with what the UI promises.
- Cover empty, loading, stale, error, and first-run states.
- Check the activation / next-step path: can the user actually do what the page tells them to do next?
- Note what already works — the report keeps it.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed 07cd1b5731f6
- 4d ago Changed · -57 lines · -57 tokens per session e14fe2d93251
- 25d ago Changed c9f3ed0d8c32
- 1mo ago First seen · 160 lines · 147 tokens per session scan A 0296a4a338c8
ux is a skill published in the GitHub repository mthines/agent-skills (20 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 1,485 once invoked, about $0.0004 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-31.
Other skills, from other repositories
custom-icons
Create or refine custom icon assets as native or traced SVGs and transparent PNG/WebP files. Use when the user asks for a bespoke icon or cohesive icon set, wants an image traced into a clean vector, or needs a detailed or 3D icon with transparency.
frontend-ui-engineering
Build production-quality, accessible, non-generic-looking UI components and pages — component composition, the state-management ladder (local to global), avoiding the recognizable "AI aesthetic," WCAG 2.1 AA accessibility, and responsive/loading/empty states. Use when building or modifying user-facing interfaces, or…
ai-design-slop-audit
This skill should be used when the user wants an evidence-backed review of an existing UI for generic "AI-generated" design defaults — asking to "audit this design", "why does this look AI-generated", "review this for design slop", or wants a removal-first cleanup plan without a speculative redesign. Point-in-time…
user-research-synthesis
Guides synthesizing raw qualitative user research into defensible themes using affinity mapping (the KJ method) and conducting Jobs-to-be-Done "Switch" interviews about past purchase decisions. Use when the user asks to "affinity map these notes", "synthesize interview findings", "cluster these observations into…
design-exploration
Generates multiple distinct design variants of a component or page, each with a completely different visual direction, then implements the chosen one. Use when the user asks to redesign, restyle, explore design options, create multiple visual directions, or compare design approaches for any UI element -- components…
animation-improvement-planning
This skill should be used when the user asks to "improve the animations", "audit the motion across the app", "make this feel better" without a specific diff to review, or wants a prioritized roadmap of animation fixes rather than a single verdict. Surveys a codebase's motion, produces a severity-ranked findings table…