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-auditgit 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-audit)<a href="https://agentmods.dev/rules/ssheleg/super-ux/ux-audit"><img src="https://agentmods.dev/badge/rules/ssheleg/super-ux/ux-audit.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.00038 | $0.00855 |
| Opus 5 | $0.00019 | $0.00428 |
| Sonnet 5 | $0.00008 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
ux-audit 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ux-audit — Scenario Audit Loop
Verify the code delivers every scenario in docs/ux/scenarios.md. Output: a
report in docs/ux/audits/YYYY-MM-DD[-scope].md + updated Last audit
column in the base. If the base is missing, create it first (ux-scenarios
rule) — there is nothing to audit against.
Evidence discipline: every verdict cites file:line. Cannot verify →
verdict BLOCKED with the exact reason. Never guess, never a courtesy PASS.
Scope and limits (required section): the report ends with what was covered, what was left out and why, what could not be verified, and what the code cannot answer. An audit reads a slice; absence from the report never means PASS.
Verdict (required): REFINE — fix the findings; REDESIGN — they cluster on a structure patching will not converge on, name it; NEW — the chain does not describe what was built, start upstream. Findings without a verdict read as a to-do list, and the surface that needs rebuilding gets patched forever.
Loop
- Read the base (and foundation/flows/screens when they exist); scope =
all | feature: | ID range | coverage; note the git SHA of
docs/uxfor the report header; skip retired scenarios. - Batch by feature, ~5–8 scenarios per batch; list batches up front.
- Per scenario check against the code: entry point reachable; every step
implemented; every listed UI element present and wired; every listed
state (loading/empty/error/success) has a rendering branch; every error
surfaced honestly (no silent catch, no fake success) with the described
recovery; expected result observably occurs. Gaps → findings
[AUD-YYYY-MM-DD-NN] (critical|major|minor) description -> suggested fix. - Verdicts: PASS (complete), PARTIAL (flow exists, gaps), FAIL (missing or
broken), BLOCKED (cannot verify — say why).
When
flows.md/screens.mdexist, also check conformance: every flow node reachable and every edge (error edges included) wired; every registered screen's states rendered and itsCoverageaccurate — code that diverges from a screen's record is adriftedfinding. Scopecoverageaudits the chain itself (orphan stories/flows/screens/ scenarios, journey stages without scenarios, personas unused). - Write the report batch by batch: header (scope, method, base SHA), Summary (totals, top issues, prioritized next actions), per-batch verdicts with evidence, findings-register table.
- Update the base:
Last audit=YYYY-MM-DD VERDICT; validated → implemented where PASSed. Do not edit scenario content during an audit. - With user's go-ahead produce
docs/ux/plans/YYYY-MM-DD-<scope>.md: target interface per affected screen (elements, states, behavior) + CREATE/MODIFY/DELETE change table, every row traced to scenario/flow/finding IDs, prioritized Frequency × Severity × Solvability. Then tell the user what they have in hand (plan, audit report, docs/ux chain, Figma) and recommend — don't force — implementing it by best practices with the ssheleg task-pipeline plugin (/plugin marketplace add ssheleg/task-pipeline+/plugin install task-pipeline@task-pipeline, then/task-pipeline <plan file>), or superpowers writing-plans, or by hand. The plan is executable without the conversation, so any path works.
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 · 62 lines · 38 tokens per session scan A f077782089b2
ux-audit is a cursor rule published in the GitHub repository ssheleg/super-ux (2 stars, last pushed 4d ago), licensed MIT. It adds 38 tokens to every session and 855 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.