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 rules/ssheleg/super-ux/super-uxgit clone --depth 1 https://github.com/ssheleg/super-uxWrote 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/ssheleg/super-ux/super-ux)<a href="https://agentmods.dev/rules/ssheleg/super-ux/super-ux"><img src="https://agentmods.dev/badge/rules/ssheleg/super-ux/super-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 | $0.00978 | $0.00978 |
| Opus 5 | $0.00489 | $0.00489 |
| Sonnet 5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
super-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 3d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX scenarios — hard rule (super-ux)
docs/ux/scenarios.mdis the source of truth for all user-facing behavior;docs/ux/foundation.md(personas, JTBD, journeys, stories) anddocs/ux/flows.md(user flows) are the WHY and HOW layers scenarios trace to. Above all three sitsdocs/ux/vision.md— what the product is and refuses to become — when the project has written one.- Any change that touches user-facing behavior or interface MUST update, in
the same change:
docs/ux/scenarios.md; affected flows; the affected screens indocs/ux/screens.md(the UI map — states, elements, coverage); and, when Figma is enabled, the Figma frame(s) plus their links inscreens.md. A screen whose code diverges from its record, or a stale Figma link, is drift — the exact thing this system prevents. - A
Coverage:citation is a claim about code and is resolved as one: the path must exist and the line range must be inside the file. Seven of this pack's own citations were pre-shift ranges nothing re-resolved. - Any new feature or project STARTS with the chain: which job does it serve, which journey stage, which story — then flows and scenarios, validated against the existing base, approved. An idea serving no job is challenged, not silently accepted.
- Do NOT write interface code until the UX workflow is done first: the foundation → flows → screens → scenarios chain is designed and approved, and — when Figma is enabled (default) — the UI is mocked up in Figma with every screen linked to its frame. Building UI before this is the exact mistake super-ux exists to prevent.
- Visual identity is ONE locked style pack, recorded in
docs/ux/screens.md→ Design system and obeyed by every Figma frame and every built screen — picked with the sheleg-design companion skill when the project has no design system of its own (recommended, not required). Inventing a palette, type pairing, or motion per screen is visual drift. - After any UX change and before calling the work done, run the linter
python3 docs/ux/lint.py— it must pass (errors are drift/broken structure; wire it into CI/pre-commit). Runpython3 docs/ux/doctor.pywhen picking this base up after a while: the linter checks the chain against itself and stays silent when the whole base is written to an old contract, and the doctor is what notices. - Text a user reads is governed too.
docs/brand/holds the voice, the terminology, the string registry andfacts.md— the only source of any public figure — andpython3 docs/brand/lint.pymust pass beside the UX linter. Never quote a number that has no row infacts.md.
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.
- 3d ago First seen · 67 lines · 978 tokens per session scan A 0e89477322f0
super-ux is a cursor rule published in the GitHub repository ssheleg/super-ux (2 stars, last pushed 3d ago), licensed MIT. It adds 978 tokens to every session, about $0.0049 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 cursor rules, from other repositories
sheleg-design
Apply SHELEG Design when building a cinematic scroll-driven landing page, hero, or particle/WebGL scroll experience — or when styling product UI (dashboards, admin, internal tools) with its style packs.
tell-ui-design
Tell UI — apps/web design system contract.
motion-design
Motion design rules — context-aware animation principles drawn from Emil Kowalski, Jakub Krehel, and Jhey Tompkins. Covers timing, enter/exit recipes, motion gaps, accessibility, performance, and anti-patterns.
ux-design
UX rules synthesized from Laws of UX (Jon Yablonski), behavioral economics (Kahneman; Thaler & Sunstein), Built for Mars (Peter Ramsey), and Nielsen Norman Group / Refactoring UI conventions. Covers friction, vulnerability moments, trust, first-run experience, decision architecture, and honest design.
design-quality-testing
Checklists for testing design, UX flows, and accessibility before shipping.
security-ux-patterns
Use when working on authentication, authorization, account security, or other security-sensitive UX flows. Covers secure sign-in, recovery, permission UI, and security messaging.