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/ux-foundationgit 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-foundation)<a href="https://agentmods.dev/rules/ssheleg/super-ux/ux-foundation"><img src="https://agentmods.dev/badge/rules/ssheleg/super-ux/ux-foundation.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.00050 | $0.00734 |
| Opus 5 | $0.00025 | $0.00367 |
| Sonnet 5 | $0.00010 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
ux-foundation 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ux-foundation — The WHY Layer
docs/ux/foundation.md holds the chain scenarios trace to: Personas
(P-NN) → Jobs to Be Done (JTBD-NN) → Customer journeys (JRN-NN) → User
stories (ST-NNN). IDs sequential, never reused; dropped entries kept, not
deleted.
Formats (ux-contract v4)
- Persona
P-NN: 1–3 sentences, grounded in data/observation, recognizable by a real user. - JTBD
JTBD-NN:When <situation>, I want to <motivation>, so I can <outcome>+ personas + type (functional|emotional|social) + forces (push/pull/anxiety/habit) + success metric (user outcome, never a feature). - Journey
JRN-NN(persona × job): stage table —# | Stage | User action | Touchpoint | Emotion (1-5) | Pain | Opportunity; end-to-end (before/during/after product); opportunity priority = Frequency × Severity × Solvability. - Story
ST-NNN:As <persona>, I want <capability>, so that <benefit>+ Traces (JTBD, JRN/stage) + Given/When/Then acceptance criteria + priority (must|should|could) + status (proposed|validated|delivered|dropped). Quality bar: INVEST.
Workflows
- Init (interview): greenfield — ask one question at a time: who uses it; what situation triggers the job; what outcome = success; walk the path end-to-end; derive stories from pains and outcomes.
- Init (reverse): existing product — reverse-engineer jobs/personas from the UI and scenarios; tag entries observed vs inferred; flag features serving no job and jobs with no support.
- Update: locate by ID, update, mark dropped (never delete), then cascade: list scenarios tracing to changed IDs and update them in the same change.
- Validate: integrity (IDs, references), quality (no features in JTBD, INVEST, observable criteria), coverage (persona→job→journey→story chain complete; must/should stories have scenarios).
Two more sections this file owns, filled when they apply: Monetization
(model + value metric + free boundary + purchase surface + money moments +
acquisition coherence — each money moment becomes a first-class flow, and a
web/web2app purchase surface makes the web funnel and the paid handoff flows
of this product too) and Design
tooling (the Figma on/off choice, default on, plus the project's Figma file
URL — asked once per project). Everything else about the visual layer, the
design system and the style pack, lives in docs/ux/screens.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 · 57 lines · 50 tokens per session scan A 449855bc3996
ux-foundation is a cursor rule published in the GitHub repository ssheleg/super-ux (2 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 734 once invoked, about $0.0003 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.