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 skills/ssheleg/super-ux/visionnpx skills add ssheleg/super-ux --skill 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/skills/ssheleg/super-ux/vision)<a href="https://agentmods.dev/skills/ssheleg/super-ux/vision"><img src="https://agentmods.dev/badge/skills/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.1 | $0.00146 | $0.01941 |
| Opus 5 | $0.00073 | $0.00971 |
| Sonnet 5 | $0.00029 | $0.00388 |
| Haiku 4.5 | $0.00015 | $0.00194 |
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 5d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vision — what the product is, and what it refuses to become
Part of super-ux — see system-map.md for the whole pipeline. After writing the document, run
python3 docs/ux/lint.py.
The layer above ux-foundation. Foundation answers who uses the product and
why; vision answers what the product is and what it refuses to
become. Without it, "should we build this?" has no answer that outlives the
person who last had an opinion.
Do not confuse it with scenarios.md, the other layer whose name starts with
"what": scenarios say what the product does, step by step. A feature can
be perfectly scenario'd and still violate the anti-vision.
This skill produces two things, and the second is the point.
docs/ux/vision.md— the document.- A vision-alignment rule in the project's own instruction file, so every later feature gets checked against the vision instead of the vision being written once and never read.
A vision nothing reads is a document, not a constraint.
Fits the chain: vision → foundation (personas, JTBD, journeys, stories) → flows → scenarios → audit. Each layer traces up to the one above it.
Step 0 — read the project, not its README
Before writing a word:
README.md,ARCHITECTURE.md,ROADMAP.md,CHANGELOG.md, everything indocs/.- Key source: entry points, main services, the schema, the routing table.
- Marketing surfaces if they exist — landing, pricing, features.
package.json/pyproject.toml/Cargo.tomlfor what it actually depends on.- The live UI. What the product does, not what it says it does.
- If
docs/ux/foundation.mdexists, read it — the vision must not contradict the personas and jobs already agreed.
A vision written from the README alone describes the README. The gap between what a project says it is and what its code does is usually where the real vision is hiding, and naming that gap out loud is often the most valuable thing this skill does.
What ships with it
1 file 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.
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.
- 5d ago First seen · 166 lines · 146 tokens per session scan A 5be8c754a445
vision is a skill published in the GitHub repository ssheleg/super-ux (3 stars, last pushed today), licensed MIT. It adds 146 tokens to every session and 1,941 once invoked, about $0.0007 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
product-designer
Expert product design covering UI/UX design, design systems, prototyping, user research, and design thinking.
website-icp-fit
You are a conversion strategist and ICP-fit auditor. You evaluate a website — either by visiting its URL or by reading its source code — to determine whether the copy, structure, messaging, and psychology are correctly aligned with the stated Ideal Customer Profile and their specific awareness stage.
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.
clinical-case-report
Structured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds"…
kami-deck
A lab-meeting deck on gut-microbiome links to sleep quality — the design, the results, the caveats, and the next experiment. Built as a decision-grade academic research deck for lab group, PI.