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-initgit 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-init)<a href="https://agentmods.dev/commands/ssheleg/super-ux/ux-init"><img src="https://agentmods.dev/badge/commands/ssheleg/super-ux/ux-init.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.00567 |
| Opus 5 | $0.00017 | $0.00283 |
| Sonnet 5 | $0.00007 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
ux-init 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.
What it actually says
Initialize the UX chain, WHAT-IT-IS → WHY → HOW → WHAT-IT-DOES:
-
Vision (offer, never assume). If
docs/ux/vision.mdis missing, ask once whether the product's direction is settled. Settled → say so and go to 1. Not settled, or the answer is "we keep arguing about scope" → invoke thevisionskill first: the anti-vision is what later stops a feature that every persona would happily use and the product should not have. Never seed an emptyvision.md— a blank vision reads as a decided one, and every later check would pass over it. -
Foundation. If
docs/ux/foundation.mdis missing or empty, invoke theux-foundationskill in Init mode — interview for greenfield, reverse-engineering for an existing product. Get the layers approved. (Tiny project and the user explicitly wants to skip? Note it and go v1 mode — scenarios without Traces.) -
Flows. Invoke the
ux-flowsskill: Design (greenfield — task analysis → mermaid flows → screen states per story) or Reverse (existing code — reconstruct actual flows with evidence, taginferred). -
Scenarios. Invoke the
ux-scenariosskill in Init mode: cover every flow node and edge (happy path, error edges, alt branches) with use-case scenarios,Traces:filled with story + flow IDs. -
Finish with the traceability check (Validate) and a status summary, then run
python3 docs/ux/lint.pyand report its counts. If avision.mdexists, confirm its alignment rule reached the project's instruction file — the linter warns when it did not. -
If the product has user-facing text, say that
docs/brand/is the layer that governs it and offer/brand-init. The chain decides what the product does; it does not decide how it speaks.
If foundation.md, flows.md, and scenarios.md already exist with
entries, do NOT reinitialize — say so and suggest /ux for the action menu
instead. If only some layers exist, initialize the missing ones and leave
the rest untouched.
Additional 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.
- 3d ago First seen · 42 lines · 35 tokens per session scan A 975e8b8c4326
ux-init is a command published in the GitHub repository ssheleg/super-ux (3 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 567 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
test
Run tests and ensure code quality for the Figma Console MCP server.
drift-check
Detect where teams are diverging from the system.
governance-review
Quarterly governance review package.
token-audit
Audit your design token architecture.
component-audit
Audit your component library inventory.
system-benchmark
Benchmark your design system across 12 scored dimensions.