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 natuleadan/skills --skill 080103-ux-standardsgit clone --depth 1 https://github.com/natuleadan/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/natuleadan/skills/080103-ux-standards)<a href="https://agentmods.dev/skills/natuleadan/skills/080103-ux-standards"><img src="https://agentmods.dev/badge/skills/natuleadan/skills/080103-ux-standards/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/natuleadan/skills/080103-ux-standards"><img src="https://agentmods.dev/badge/skills/natuleadan/skills/080103-ux-standards.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.00036 | $0.00595 |
| Opus 5 | $0.00018 | $0.00298 |
| Sonnet 5 | $0.00007 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
080103-ux-standards 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 12d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Standards
Production-grade UX standards for web and mobile: accessibility, interaction, form design, navigation architecture, copy, and cognitive load.
References
| Topic | File |
|---|---|
| WCAG accessibility: contrast 4.5:1, focus, keyboard, screen reader, ARIA, reduced motion | references/accessibility.md |
| Touch interaction: targets 44×44pt, gestures, haptics, safe areas, platform standards | references/touch-interaction.md |
| Form UX: labels, validation, error recovery, progressive disclosure, keyboard, autofill | references/form-ux.md |
| Navigation: bottom nav, sidebar, breadcrumbs, back stack, deep linking, adaptive patterns | references/navigation-patterns.md |
| UX writing: error messages, empty states, CTAs, confirmation, tone | references/ux-writing.md |
| Cognitive load: information density, chunking, progressive disclosure, decision fatigue | references/cognitive-load.md |
Core Rules
- Accessibility is critical: Color contrast ≥4.5:1, visible focus rings, keyboard nav, aria-labels, skip links, heading hierarchy never skips levels. Color is never the only indicator.
- Touch targets: Minimum 44×44pt (Apple) / 48×48dp (Material). 8px minimum gap between targets. Don't rely on hover alone.
- Forms: Visible labels (not placeholder-only), errors below the field, progressive disclosure, validate on blur, input types trigger correct keyboard.
- Navigation: Bottom nav ≤5 items, labels + icons. Back must preserve scroll/state. All screens reachable via deep link.
- UX writing: Every word earns its place. Errors state cause + how to fix. Empty states teach the interface.
When to Use
| Trigger | Use |
|---|---|
| Designing forms or inputs | references/form-ux.md |
| Building navigation structure | references/navigation-patterns.md |
| Reviewing accessibility | references/accessibility.md |
| Writing UI copy | references/ux-writing.md |
| Evaluating information density | references/cognitive-load.md |
| Mobile/touch design review | references/touch-interaction.md |
What ships with it
8 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.
- 12d ago First seen · 40 lines · 36 tokens per session scan A 81bf9679761c
080103-ux-standards is a skill published in the GitHub repository natuleadan/skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 595 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 skills, from other repositories
hmi-design-full
Comprehensive ISA-101 design rules for Human Machine Interfaces in process automation, with detailed reference files covering color design, display hierarchy, navigation, alarms, human factors, performance, and lifecycle management. Use when designing, building, reviewing, or generating code for HMIs, control system…
hmi-design-light
ISA-101 design rules for Human Machine Interfaces in process automation, covering display hierarchy, color standards, alarm integration, navigation, and situation awareness. Use when designing, building, reviewing, or generating code for HMIs, control system displays, SCADA screens, operator dashboards, or industrial…
design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…
component-family-consistency
Buttons, inputs, pills, badges, calendars, and other interactive components form a visual family — they share the same border-radius, colour logic, shadow scale, border style, and spacing rhythm. Inconsistency between them breaks the sense of a coherent product. Use when building or reviewing a component library…
modular-scale-typography
Typography feels cohesive and intentional when font sizes follow a modular scale — a ratio-based sequence where every size is mathematically related to the others. Use when defining type scales, setting up design tokens, reviewing font size choices, or when typography feels inconsistent or arbitrary.
extract-design
Extract a complete design system — colors, typography, spacing, components, shadows, and W3C design tokens — from any live website using Dembrandt. Runs a headless browser against the URL and returns real computed values from the DOM. Use when you need a site's actual design tokens, want to reverse-engineer a visual…