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/visiongit 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/vision)<a href="https://agentmods.dev/commands/ssheleg/super-ux/vision"><img src="https://agentmods.dev/badge/commands/ssheleg/super-ux/vision.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.00022 | $0.00254 |
| Opus 5 | $0.00011 | $0.00127 |
| Sonnet 5 | $0.00004 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
vision 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
Run the vision skill for this project.
It sits above ux-foundation: foundation answers who uses the product and why,
vision answers what the product is and what it refuses to become.
- Read the project properly first — README, architecture, roadmap, key source,
the live UI, and
docs/ux/foundation.mdif it exists. Not the README alone. - Write
docs/ux/vision.mdin the nine layers, the anti-vision included — it is the layer teams skip and the only one that settles arguments. - Validate against the checklist; a contradiction with
foundation.mdis a finding to raise, not to smooth over. - Install the vision-alignment rule into the project's OWN instruction file
(
CLAUDE.md/AGENTS.md/GEMINI.md— whichever it already uses). Idempotent. Never hardcode one agent's path. - Link it from the README.
$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 · 23 lines · 22 tokens per session scan A 0e26fc1dc066
vision is a command published in the GitHub repository ssheleg/super-ux (2 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 254 once invoked, about $0.0001 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-case-study
Generate a project case study in pure-monochrome editorial format. Triggers on "write a case study", "case study this project", "do the wrap-up doc". Use when writing a project case study, shipping a publishable Wfrah-editorial document, ending a project with a case-study artifact, producing the (A)–(G) section format…
ux-component
Generate a single component (button, modal, navbar, sidebar, card, table, form, chart) from a spec. Triggers on "build a [component]", "create a pricing card", "make a modal", "add a navbar". Use when generating a single component, the user says "create a [button/modal/navbar/card/table/form/chart]", embedded into an…
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-image-to-code
Take a design reference image (PNG/JPG/WebP), extract its dominant palette + canvas polarity + type signal via pure Pillow CV, match the result against the v2 palettes/styles manifests, and run the recommender on the synthetic brief. Returns the closest palette, the closest style, and a full recommended design system…