Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Laith0003/ux-skillnpx agentmods add commands/laith0003/ux-skill/ux-auditWrote 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-audit)<a href="https://agentmods.dev/commands/laith0003/ux-skill/ux-audit"><img src="https://agentmods.dev/badge/commands/laith0003/ux-skill/ux-audit.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.00143 | $0.03289 |
| Opus 5 | $0.00072 | $0.01644 |
| Sonnet 5 | $0.00029 | $0.00658 |
| Haiku 4.5 | $0.00014 | $0.00329 |
Grade A, and why
ux-audit scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Read, Write, Edit, Bash(ls:*), Bash(cat:*), Bash(find:*), Bash(mkdir:*), Bash(curl:*), Bash(date:*), Glob, Grep, Task, WebFetch How it starts
The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ux-audit
You are running the /ux-audit command from the ux plugin. The job is a structured, opinionated review of a surface against six lenses, producing findings the user can act on.
When to use
Triggers: "audit", "review the ux", "is this any good", "what's broken", "audit this page", "ux review", "tear this apart".
Use when the surface already exists (live URL, mockup, code, screenshot) and the user wants a structured, defensible critique with severity-tagged findings. Not for taste calls — that is /ux-critique. Not for a single dimension — use /ux-copy, /ux-a11y, /ux-motion, or /ux-polish for narrow scopes.
Input
One of: a URL, an absolute file path to code or a markup file, a screenshot path, a code snippet pasted in chat, or a free description. If multiple, treat them as the same surface.
If .ux/last-frame.json exists, read it first — audience and outcome anchor every finding's severity.
Process
1. Anchor to the framing
Read .ux/last-frame.json if present. If absent and the surface clearly needs framing context, suggest running /ux-frame first — but proceed if the user insists.
2. Read the surface
- URL → fetch the page (WebFetch or the browser MCP if available).
- File path → read the file.
- Screenshot → look at the image.
- Code snippet → use as-is.
- Description → ask one clarifying question if too vague to inspect, then proceed.
3. Run the six lenses in order
For each lens, identify findings, cite which principle each finding violates, write evidence (what you saw) and a fix (what to do).
Lens 1 — FRAME
Reference: references/process/lean-ux-gothelf.md and references/process/lean-ux-klein.md.
Check: does the surface match the audience and outcome from the framing? Is the hypothesis observable in the surface? Is the success signal supported by what the user can do here?
If the framing is missing, this lens checks: does the surface have a clear "who is this for and what changes for them?" signal — or is it generic?
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 · 289 lines · 143 tokens per session scan A a4fe4fe15755
ux-audit is a command published in the GitHub repository Laith0003/ux-skill (66 stars, last pushed today), licensed MIT. It adds 143 tokens to every session and 3,289 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
test
Run tests and ensure code quality for the F-MCP ATezer server.