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 skills add ssheleg/super-ux --skill ux-scenariosgit 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/skills/ssheleg/super-ux/ux-scenarios)<a href="https://agentmods.dev/skills/ssheleg/super-ux/ux-scenarios"><img src="https://agentmods.dev/badge/skills/ssheleg/super-ux/ux-scenarios/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/skills/ssheleg/super-ux/ux-scenarios"><img src="https://agentmods.dev/badge/skills/ssheleg/super-ux/ux-scenarios.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.00112 | $0.02284 |
| Opus 5 | $0.00056 | $0.01142 |
| Sonnet 5 | $0.00022 | $0.00457 |
| Haiku 4.5 | $0.00011 | $0.00228 |
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 yesterday.
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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ux-scenarios — Maintain the Scenario Base
Part of super-ux — see system-map.md for the whole pipeline and the four sync rules. After changes, run the linter (
python3 docs/ux/lint.py).
AI-generated interfaces go bad when UI is built without a model of user
behavior. This skill keeps one: docs/ux/scenarios.md in the target project
is the source of truth for everything the user can do, see, and hit — every
feature, every button, every state, every error, every result.
Format contract: scenario-format.md (ux-contract v4). Read it before writing or editing scenarios. Never deviate from its field names, ID rules, statuses, or checklists.
The WHY and HOW layers: when docs/ux/foundation.md exists (personas,
JTBD, journeys, stories — ux-foundation skill) and/or docs/ux/flows.md
(task analysis, user flows — ux-flows skill), scenarios are derived FROM
them: one scenario set per flow, covering the happy path, every error edge,
and every alt branch of the flow diagram; Traces: filled with story + flow
IDs; traceability rules enforced (every must/should story covered; every
flow node/edge covered; every scenario serves a story or job — a scenario
serving nothing is a candidate for deletion, not implementation). Steps are
written use-case style: user action -> observable system response. If the
upper layers are missing on a non-trivial product, recommend ux-foundation
→ ux-flows first; proceed in v1 mode (no Traces) only for tiny projects
or on explicit user choice.
Design taste: apply ux-design-principles.md — states per screen, error recovery, primary-action rules — when writing Expected results and Errors & recovery.
The hard rule
- Scenarios come BEFORE interface. A new feature or project starts with drafting scenarios and validating them against the existing base — conflicts, overlaps, gaps — and getting them approved. Only then design and build UI.
- Any change touching user-facing behavior updates
docs/ux/scenarios.mdin the SAME change. New behavior with no scenario is a blocker, not a warning.
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/best-practices-index.md 25 KB
- references/best-practices.md 173 KB
- references/component-guidelines.md 7.1 KB
- references/figma-integration.md 10 KB
- references/figma-structure.md 5.4 KB
- references/interactive-flow-prototypes.md 4.6 KB
- references/practice-selection.md 12 KB
- references/prototype-walkthrough.md 2.5 KB
- references/scenario-format.md 46 KB
- references/state-stress-matrix.md 3.8 KB
- references/system-map.md 8.3 KB
- references/ux-design-principles.md 13 KB
- references/visual-identity.md 8.1 KB
- templates/scenarios.md 1.5 KB
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.
- yesterday Changed · +13 lines 16cb3486dcdf
- 4d ago Changed · +4 lines dbdf9cfbe788
- 11d ago First seen · 177 lines · 112 tokens per session scan A 469914a84ea5
ux-scenarios is a skill published in the GitHub repository ssheleg/super-ux (3 stars, last pushed yesterday), licensed MIT. It adds 112 tokens to every session and 2,284 once invoked, about $0.0006 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 skills, from other repositories
wireframing
Low/high fidelity wireframes, user flows, information architecture, prototyping techniques, and design iteration processes.
product-design
Design de produto nivel Apple — sistemas visuais, UX flows, acessibilidade, linguagem visual proprietaria, design tokens, prototipagem e handoff. Cobre Figma, design systems, tipografia, cor, espacamento, motion design e principios de design cognitivo.
fs-electric-studio
OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.
kami-landing
Produce a print-grade single-page kami (紙 / 纸) document — warm parchment canvas, ink-blue accent, serif at one weight, no italic, no cool grays. The output reads like a professional white paper or studio one-pager, not an app UI. Multilingual by design (EN · zh-CN · ja). One self-contained HTML file, zero dependencies.
hps-memphis-pop
A pop-culture retrospective on how 1980s design language shaped today's apps — the scenes, the turning point, and the takeaway. Built as a decision-grade story deck for talk audience, design community.
ve-terminal-mono
OpenDesign from the CLI: driving the full design workflow with the od command — scripted, composable, agent-ready. Built as a decision-grade AI literacy deck for developers, power users.