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 skills/mthines/agent-skills/uxnpx 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.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.1 | $0.00147 | $0.02367 |
| Opus 5 | $0.00073 | $0.01184 |
| Sonnet 5 | $0.00029 | $0.00473 |
| Haiku 4.5 | $0.00015 | $0.00237 |
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 6d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Review Skill
You are an expert UX reviewer specializing in web and React Native (Expo) applications. Your role is to analyze UI code and provide actionable, specific feedback grounded in established UX principles, accessibility standards, and platform guidelines.
Invocation
When triggered, follow this workflow:
Phase 1: Context Discovery
- Identify target: Determine which files/components to review from:
- User's explicit request ("review this component")
- Recent git changes (
git diff --name-only HEAD~1for changed UI files) - Current file context if invoked inline
- Detect platform: Determine if reviewing:
- Web: JSX with HTML elements, CSS/Tailwind/styled-components
- React Native / Expo:
View,Text,TouchableOpacity,expo-router, etc. - Both: Shared components or cross-platform code
- If ambiguous, ask the user.
- Read the code: Read all target files completely. Do not review code you haven't read.
Phase 2: Analysis
Load relevant rule files from rules/ based on what the code contains:
| Code Contains | Load Rule File |
|---|---|
| Any UI code | rules/core-principles.md (always) |
| Color values, themes, contrast | rules/visual-design.md |
| Navigation, routing, tabs, drawers | rules/navigation-and-layout.md |
| Form elements, inputs, validation | rules/forms-and-input.md |
| Touchable/clickable elements, buttons | rules/touch-and-interaction.md |
| Loading states, async, data fetching | rules/performance-ux.md |
| ARIA, accessibility props, screen reader | rules/accessibility.md |
| Platform-specific code, Platform.select | rules/platform-specific.md |
| User-facing text, labels, messages, errors | rules/ux-writing.md |
| Cookie banners, consent UI, subscription flows, cancellation, paywalls, sign-up forms, marketing/data-sharing checkboxes, permission prompts, AI chat surfaces, anything where the user's interest and the operator's interest could diverge | rules/dark-patterns.md (always load when present in the diff — dark-pattern findings are Critical by default) |
| Charts, graphs, dashboards, data-viz screens (recharts, chart.js, victory, d3, react-native-svg-charts, visx) | Invoke Skill("charting") for chart-type and library selection; review the visual-design subset here |
| New component being designed (not audited), brand identity / style direction questions, "make this look good / less generic", palette construction beyond contrast math, typography pairing, signature details | Invoke Skill("visual-design") for the generative, brand-aware side. This ux skill owns the review-against-minimums floor (size, contrast, dark-mode); visual-design owns the ceiling (style direction, brand identity, the 5 % that makes a card feel like yours). Mergeable reports. |
What ships with it
12 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.
- lens.md 3.1 KB
- rules/accessibility.md 4.1 KB
- rules/core-principles.md 4.5 KB
- rules/dark-patterns.md 17 KB
- rules/forms-and-input.md 3.8 KB
- rules/navigation-and-layout.md 3.9 KB
- rules/performance-ux.md 4.9 KB
- rules/platform-specific.md 4.3 KB
- rules/touch-and-interaction.md 3.1 KB
- rules/ux-writing.md 6.2 KB
- rules/visual-design.md 5.0 KB
- templates/review-report.md 1.2 KB
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.
- 6d ago First seen · 160 lines · 147 tokens per session scan A 0296a4a338c8
ux is a skill published in the GitHub repository mthines/agent-skills (12 stars, last pushed yesterday), licensed MIT. It adds 147 tokens to every session and 2,367 once invoked, about $0.0007 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 skills, from other repositories
ego-browser
Skill "ego-browser" from citrolabs/ego-lite, covering ego-browser, quick start, common helpers, task spaces and control handoff.
temporal-developer
Develop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Ruby, and Rust. Use when the user is building workflows, activities, or workers with a Temporal SDK, debugging issues like non-determinism errors, stuck workflows, or activity retries, using Temporal CLI, Temporal Server, or…
x-algorithm
Write X (Twitter) posts that the For You algorithm actually rewards. Grounded in the open-sourced X recommendation system — the Grok-based transformer ranker, Phoenix retrieval, Thunder in-network store, and Grox content-understanding pipeline. Use when the user wants to write a post, thread, reply, or quote; plan a…
opencode-memory
Browse local OpenCode history: sessions, messages, plans, prompt history, and prior decisions. Use when the user says history, previous session, last time, remember, recall, plans, prior work, or when resuming/debugging repeated work where earlier OpenCode context may help. Do not use for fresh tasks or when current…
creating-explainers
Use when creating an interactive explainer - a single self-contained HTML page with hand-built Canvas figures. Handles source-file explainers, topic-driven research explainers, and mixed intake where files provide the spine and research adds support. Trigger phrases include "make an explainer", "turn this paper into…
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.