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/laith0003/ux-skill/ux-nextgit clone --depth 1 https://github.com/Laith0003/ux-skillWrote 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/laith0003/ux-skill/ux-next)<a href="https://agentmods.dev/commands/laith0003/ux-skill/ux-next"><img src="https://agentmods.dev/badge/commands/laith0003/ux-skill/ux-next.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.00102 | $0.01795 |
| Opus 5 | $0.00051 | $0.00898 |
| Sonnet 5 | $0.00020 | $0.00359 |
| Haiku 4.5 | $0.00010 | $0.00179 |
Grade A, and why
ux-next 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 6d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ux-next
You are running the /ux-next command from the ux plugin. The job is to read the project's accumulated UX state and tell the user the highest-leverage next move. You are a conductor, not a builder. Read-only.
When to use
Triggers: "what should I do next", "what's the next move", "decide for me", "where do we go from here", "/ux-next", or any moment the user is between commands and asks for direction.
Input
Optional — if the user names a specific report ("look at the a11y report"), focus there. Default: scan every .ux/last-*.json and decide.
Process
1. Scan state
List .ux/last-*.json in the project root. If the directory does not exist, output the empty-state response (see Failure modes) and stop.
For each report, read it. Keep in memory:
- The command that produced it
- Timestamp
- Counts of unfixed Critical / High / Medium / Low findings
- Any explicit
ship_readinessorgo_no_gosignal - Any explicit
next_recommendedfield
2. Score leverage
Score each report on three axes:
- Severity — sum of
(Critical * 4) + (High * 2) + (Medium * 1)for unfixed findings - Recency — newer reports score higher; reports older than 14 days are halved
- Blocking signal — if any report says "ship-readiness: no-go" or "blockers present," it gets +10
Pick the report with the highest leverage score. The next command is the one that directly addresses that report's blockers.
3. Map report to next command
| Source report | Highest-leverage next command |
|---|---|
last-a11y.json with Critical findings |
/ux-a11y --fix |
last-polish.json with open items |
/ux-polish --apply |
last-motion.json flagging jank |
/ux-motion --fix |
last-design.json with no follow-up |
/ux-polish then /ux-a11y |
last-research.json with results pending |
/ux-research --synthesize |
last-workshop.json with a Game Plan |
/ux-design (first MVP) or /ux-frame |
last-component.json standalone |
/ux-component (next one) or /ux-design (assemble) |
last-dashboard.json with Critical |
/ux-polish or /ux-a11y |
last-system.json newly built |
/ux-component (build against it) |
last-case-study.json complete |
/ux-expert (share) or done |
| Nothing actionable, all green | /ux-next done (call it shipped) |
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.
- 6d ago First seen · 161 lines · 102 tokens per session scan A 2e68d2017c5c
ux-next is a command published in the GitHub repository Laith0003/ux-skill (66 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 1,795 once invoked, about $0.0005 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-30.
Other commands, from other repositories
ds-add
Kullanıcı bir Figma linki ile yeni tasarım sistemi eklemek istediğinde bu komutu kullan. Bu komut yeni ekleme ve güncelleme arasındaki farkı otomatik tespit eder.
ds-sync
Mevcut bir tasarım sistemi kütüphanesini Figma'dan senkronize eder. Tam sync, kısmi sync ve resume (yarım kalanı devam ettirme) destekler.
ds-validate
Kullanıcı "kütüphane doğrula", "DS'i validate et", "cache'i kontrol et", "DS uyumunu denetle" dediğinde bu komutu uygula. Eklenmiş DS'lerin repo template + user-local cache + state dosyalarının birbiriyle tutarlı olduğunu denetler.
add-library
Kullanıcı "kütüphane ekle", "library ekle", "tasarım sistemi ekle", "design system ekle" dediğinde bu komutu uygula.
setup-rest-token
Kullanıcı "REST token kur", "REST token setup", "FIGMARESTTOKEN nasıl ayarlanır", "component discovery hızlandır" dediğinde bu komutu uygula.
install-library
Kullanıcı "kütüphane kur", "library kur", "library install", "kütüphane yükle", "kütüphane güncelle" dediğinde veya bir .md dosya yolu verip "bunu kur" dediğinde bu komutu uygula.