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/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/ux-scenarios)<a href="https://agentmods.dev/rules/ssheleg/super-ux/ux-scenarios"><img src="https://agentmods.dev/badge/rules/ssheleg/super-ux/ux-scenarios.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.00042 | $0.00781 |
| Opus 5 | $0.00021 | $0.00391 |
| Sonnet 5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
ux-scenarios 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 8d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ux-scenarios — Maintain the Scenario Base
docs/ux/scenarios.md describes everything the user can do, see, and hit —
every feature, button, state, error, result. Keep it true.
File structure (ux-contract v4)
Title, then header comment, then: Index table
(| ID | Title | Feature | Persona | Traces | Status | Last audit |),
Personas (pointer to foundation.md when it exists, else defined here),
Scenarios grouped by feature.
When docs/ux/foundation.md exists, scenarios derive from it: draft per
user story / journey stage, fill Traces: (e.g. ST-001 (JTBD-01, JRN-01/#2)), enforce traceability — every must/should story covered by ≥1
scenario, every scenario serves ≥1 story or job.
Scenario entry fields (exact names): Persona, Feature, Traces, Entry point,
Preconditions, Steps (numbered, one user action each, paired with the
observable system response), Expected result (observable), Alt paths
(meaningful non-error deviations — skip/dismiss/alternate route — omit only
when none exist), UI elements (every button/field/link/dialog/toast involved —
this is what audits check), States covered (loading|empty|error|success),
Errors & recovery (each failure: what the user sees, how they recover),
Status (draft|validated|implemented|retired), Coverage (file:line or
none yet).
Rules: IDs SCN-NNN, sequential, never reused; retired entries are kept,
never deleted. Lifecycle: draft → validated (human approval) → implemented
(audit-confirmed); changed scenarios drop back to draft.
Per-feature completeness: happy path, every error path, empty state, visible loading, destructive-action confirmation, returning-user variant. Per-product: first-run onboarding, every core flow, settings, multi-entity flows (e.g. second project), account/data lifecycle, and — when the product earns money — the monetization flows: paywall (first-session placement), trial start/end, upgrade-at-limit, cancel + winback, rating prompt after success moments, plus the web funnel (landing, pricing, signup, checkout, abandonment, failed payment) and the paid handoff with its failure branches when money is taken on the web.
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.
- 8d ago First seen · 62 lines · 42 tokens per session scan A 54a6146605d5
ux-scenarios is a cursor rule published in the GitHub repository ssheleg/super-ux (3 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 781 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 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.