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 commands/ssheleg/super-ux/ux-flowsgit 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/commands/ssheleg/super-ux/ux-flows)<a href="https://agentmods.dev/commands/ssheleg/super-ux/ux-flows"><img src="https://agentmods.dev/badge/commands/ssheleg/super-ux/ux-flows.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.00035 | $0.00307 |
| Opus 5 | $0.00017 | $0.00153 |
| Sonnet 5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
ux-flows 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 4d 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.
What it actually says
Invoke the ux-flows skill.
If this is design/improve work and the foundation has no Figma choice recorded, ask once whether to mock up in Figma (default yes); when enabled, mirror each screen into a Figma frame applying the visual-craft practices and link every screen row to its frame.
Settle the visual identity before drawing anything: read screens.md →
Design system → Style pack, and when it's empty pick one with the
sheleg-design companion skill (offer its one-time install if missing —
recommend, don't force) and record the pack + its token file. Frames and
built screens use that pack's tokens instead of a per-screen palette.
Pick the workflow from state and $ARGUMENTS: stories exist but flows
don't → Design; existing product without flows.md → Reverse; $ARGUMENTS
says improve/fix/redesign → Improve (heuristic evaluation PRN-01..24 →
traced before/after proposals); otherwise → Update.
After flow changes, cascade to ux-scenarios: every new/changed node and
edge needs scenario coverage in the same session.
Context from the user: $ARGUMENTS
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.
- 4d ago First seen · 28 lines · 35 tokens per session scan A 6f5238a76fb7
ux-flows is a command published in the GitHub repository ssheleg/super-ux (3 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 307 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 commands, from other repositories
ux-motion
Animation and motion rubric. Checks timing, easing, meaning, reduced-motion compliance, and performance for every animation on a surface. Triggers on "motion check", "are the animations good", or "fix the motion". Use when auditing motion or animations, checking durations / easing / reduced-motion / performance, is…
ux-copy
Microcopy review and rewrite against the voice rubric. Produces a before/after table with severity per string and a clean rewrite block. Triggers on "review the copy", "fix the microcopy", "the error messages are bad", or "rewrite this". Use when reviewing or rewriting microcopy, fixing error messages that sound like…
ux-system
Propose a complete starter design system for a project that doesn't have one. Triggers on "we don't have a design system", "build us a system", "propose tokens", "what should our theme be". Use when proposing a starter design system, generating tokens / foundations / components from a brand brief, the project has no…
ux-recommend
The v2 flagship. Runs the 5-parallel-search Python engine across 11 data manifests (75+ styles, 170+ palettes, 65+ type pairs, 120+ components, 170+ industries, 110+ UX laws, 50+ motion presets, 120+ anti-patterns, 92 brand specs) and returns a complete recommended design system for your project — with always-on…
ui-audit
Comprehensive UI audit for accessibility, consistency, and usability.
error-analysis
You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.