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-fixgit 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-fix)<a href="https://agentmods.dev/commands/laith0003/ux-skill/ux-fix"><img src="https://agentmods.dev/badge/commands/laith0003/ux-skill/ux-fix.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.00129 | $0.03544 |
| Opus 5 | $0.00064 | $0.01772 |
| Sonnet 5 | $0.00026 | $0.00709 |
| Haiku 4.5 | $0.00013 | $0.00354 |
Grade A, and why
ux-fix 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ux-fix
You are running the /ux-fix command from the ux plugin. The job is to take a report already produced by another ux-* command, apply its findings as atomic commits via the right sub-agents, and re-verify by re-running the originating command.
When to use
Triggers: "fix the findings", "apply the fixes", "run the fix loop", "patch the surface", "make the changes", "go fix it".
Use after running /ux-audit, /ux-copy, /ux-a11y, /ux-motion, or /ux-polish and reviewing the findings. The user has decided to act; this command is the act.
Do not use without an existing report. If .ux/ has no last-*.json file, return an error and direct the user to run an audit command first.
Input
Optional: which report to act on (--from audit | copy | a11y | motion | polish). If unspecified, auto-detect by reading every .ux/last-*.json file and picking the most recent timestamp.
Optional: --include-cosmetic to include Cosmetic-severity findings (default skips them).
Optional: --max <n> to cap the number of fixes per run (default: all eligible findings).
Process
1. Locate the source report
If --from is set, read .ux/last-<name>.json directly.
If not, list every .ux/last-*.json, parse timestamps, pick the most recent. Surface to the user which report is being acted on:
Acting on .ux/last-<name>.json (timestamp: <ISO>)
<n> findings — <Critical>/<High>/<Medium>/<Cosmetic>
If the latest report is older than 24 hours, warn the user — the surface may have changed since the report was generated. Ask for confirmation to proceed, or recommend re-running the originating command first.
2. Validate clean working tree
Run git status --short. If the tree is dirty:
- Show the user what is dirty.
- Offer three options:
- Commit — let the user commit the existing changes first before starting the fix loop.
- Stash —
git stash push -m "ux-fix pre-loop stash"and proceed; restore at the end. - Abort — exit without applying any fixes.
- Wait for the user's choice. Do NOT proceed silently with a dirty tree.
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 · 310 lines · 129 tokens per session scan A df03774e3aca
ux-fix is a command published in the GitHub repository Laith0003/ux-skill (66 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 3,544 once invoked, about $0.0006 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.