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-polishWrote 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-polish)<a href="https://agentmods.dev/commands/laith0003/ux-skill/ux-polish"><img src="https://agentmods.dev/badge/commands/laith0003/ux-skill/ux-polish.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.00110 | $0.03811 |
| Opus 5 | $0.00055 | $0.01906 |
| Sonnet 5 | $0.00022 | $0.00762 |
| Haiku 4.5 | $0.00011 | $0.00381 |
Grade A, and why
ux-polish 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 8d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ux-polish
You are running the /ux-polish command from the ux plugin. The job is a cosmetic pass — the surface mostly works but feels rough, generic, or unfinished. Tighten spacing, sharpen hierarchy, kill AI-slop tells, and align loose tokens.
When to use
Triggers: "polish", "tighten this up", "remove the AI-slop", "make it premium", "make this less AI-looking", "the spacing feels off", "this looks generic", "needs more taste", "the design feels cheap".
Use when the structure is right but the execution is loose. Not for fundamental problems (use /ux-audit or /ux-design). Not for copy issues (use /ux-copy). Not for motion (use /ux-motion). Not for accessibility (use /ux-a11y).
If a /ux-critique or /ux-audit has surfaced structural issues, run those first — polish on a broken structure is wasted work.
Input
One of: a URL, an absolute file path containing the code, a screenshot, or a code snippet. Code is preferred for token consistency checks; a URL or screenshot is preferred for visual rhythm.
Process
1. Run the AI-slop tell list
Scan the surface for these specific tells. Each found tell is a Critical or High finding depending on visibility.
Typography slop
- Inter where wrong: Inter is fine for utilitarian dashboards but feels generic on landing pages, marketing, brand surfaces. Look for Inter being used as the only typeface — that is the tell.
- Generic sans pairing: Inter + a "modern serif" with no character (Playfair, Lora, default Google Fonts serif). Editorial surfaces need stronger pairings.
- System UI without intent: defaulting to
-apple-system, BlinkMacSystemFontwhen the surface needs voice. - Centered everything: every heading, every paragraph, every CTA centered. Even when there is no reason.
Color slop
- Purple-blue gradients: the AI default.
#6366f1 → #8b5cf6or any variant. The single strongest tell. - Pure black:
#000orbg-black. Should be Zinc-950, Charcoal, Off-Black. - Saturated accent colors: anything over 80% saturation reads as generic.
- Multiple chromatic accents: a brand uses one accent. Two is loud. Three is a tell.
- Tailwind defaults uncustomized:
bg-blue-500,text-gray-500everywhere. Even the colors are confessing.
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.
- 8d ago First seen · 277 lines · 110 tokens per session scan A feacb048213a
ux-polish is a command published in the GitHub repository Laith0003/ux-skill (68 stars, last pushed 2d ago), licensed MIT. It adds 110 tokens to every session and 3,811 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
design-screen
Design a complete screen layout from a description or requirements.
responsive-audit
Audit a design's responsive behaviour across breakpoints — layout, touch targets, and content reflow.
color-specialist
Use when colour is failing. Contrast below AA, a palette with no system behind it, dark mode that is only inverted light mode, or semantic colours that carry no meaning.
motion-designer
Use when animation feels wrong. Transitions too slow or too bouncy, motion with no purpose, blanket transitions on every property, no reduced-motion support, or animation that drops frames.
spacing-layout-specialist
Use when spacing looks arbitrary. Padding and margins off any scale, inconsistent gaps between the same components, no grid underneath, or a layout that needs a denser mode.
typography
Run a typography-only audit — scale detection, font count, body size, line height, fluid type. Scoped variant of /ui-ux-suite:audit.