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.
git clone --depth 1 https://github.com/kok-o/koko-contextos-agentsWrote 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/rules/kok-o/koko-contextos-agents/ux-design)<a href="https://agentmods.dev/rules/kok-o/koko-contextos-agents/ux-design"><img src="https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/ux-design/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/rules/kok-o/koko-contextos-agents/ux-design"><img src="https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/ux-design.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.00000 | $0.00779 |
| Opus 5 | $0.00000 | $0.00390 |
| Sonnet 5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
ux-design 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: UX Design
UX Design
Overview
A brief summary of what the skill does and its core philosophy.
When to Use
Context for when this skill is applicable.
Rules & Patterns
UX Design — Best Practices
Information Architecture
- Mental models — organize content the way users think, not the way your code is structured
- Card sorting — group features into logical categories
- Navigation structure — no more than 3 clicks to any page
- Naming — use user's language, not internal jargon
User Flows
Design every state
Every screen has 5 states. Design ALL of them:
- Empty state — first visit, no data yet. Include CTA to get started
- Loading state — skeleton screens > spinners
- Partial state — some data, not complete
- Ideal state — normal usage with data
- Error state — what went wrong and how to fix it
Reduce cognitive load
- Progressive disclosure — show only what's needed now
- Sensible defaults — pre-fill what you can
- Inline help — tooltips and contextual guidance
- Confirmation for destructive actions — but NOT for every action
Forms UX
- Show progress for multi-step forms
- Validate inline (on blur), not on submit
- Show password requirements as the user types
- Auto-focus the first input
- Use appropriate input types (email, tel, date)
- Disable submit button only when form is submitting, never as "validation"
Onboarding
- Quick win — let users see value within 30 seconds
- Minimal signup — only ask for what's absolutely needed
- Progressive onboarding — teach features as users encounter them
- Skip option — always let users skip tutorials
Feedback
- Every action needs feedback (success, error, pending)
- Use toast notifications for non-blocking feedback
- Use inline messages for form validation
- Loading states should be < 300ms before showing (avoid flash)
- Optimistic UI for fast-perceived actions
Mobile UX
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 · 120 lines · 0 tokens per session scan A 8c984c0fd833
ux-design is a cursor rule published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 779 tokens. 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-09-03.
Other cursor rules, from other repositories
align-grid
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid…
extract-design
Extract a Google DESIGN.md file from an HTML prototype (claude.ai/design or any styled page) using Puppeteer, producing machine-readable tokens and AI-generated prose. Use when the user has an HTML prototype and wants a DESIGN.md to anchor their project's visual identity, or when seed-conventions has just scaffolded a…
hatch3r-design-system-detection
Mandatory detection of existing design tokens, theme primitives, and component library before AI agents author new UI components.
hatch3r-ux-states-and-flows
Four-state surface contract (loading/empty/error/partial), user-flow decomposition before implementation, and microcopy + tone discipline for end-user UIs.
hatch3r-ai-ux-patterns
2026 AI/agentic UX patterns for end-user projects shipping AI features — streaming, tool-call UI, human-approval gates, cancel/abort/undo, citations.
hatch3r-accessibility-standards
Accessibility standards covering WCAG 2.2 AA compliance, keyboard navigation, screen readers, and ARIA patterns.