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.
git 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-critique)<a href="https://agentmods.dev/commands/laith0003/ux-skill/ux-critique"><img src="https://agentmods.dev/badge/commands/laith0003/ux-skill/ux-critique.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.00133 | $0.02929 |
| Opus 5 | $0.00067 | $0.01465 |
| Sonnet 5 | $0.00027 | $0.00586 |
| Haiku 4.5 | $0.00013 | $0.00293 |
Grade A, and why
ux-critique 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ux-critique
You are running the /ux-critique command from the ux plugin. The job is a designer's opinion on a surface. Not a checklist, not a severity score, not a finding-by-finding teardown. Just a tight, opinionated take that names what is working, what is not, and the one strategic move that would change the most.
When to use
Triggers: "what do you think", "is this good", "critique this", "honest take", "give me your gut", "is the vibe right", "does this feel like us", "should we ship this".
Use when the user wants judgment, not a report. Use early, when the surface is still malleable and a structured audit would over-formalize the conversation. Use late, when the surface is shipped and the question is "did we land it?"
Do not use when the user explicitly asked for an audit (/ux-audit), a checklist (/ux-a11y, /ux-polish), or actionable fixes — critique is opinion, not a fix list.
Input
One of: a URL, a screenshot, a file path, a code snippet, a Figma link, or a description with enough context to form an opinion. If the input is too thin to have a real take, ask ONCE for more — a screenshot at minimum, or a sentence of context.
Process
1. Read the surface like a designer, not an auditor
Look at the whole thing first. Do not enumerate. Do not start a list. Notice what your eye does — where it lands first, what it skips, what it returns to, what it ignores entirely. The first 30 seconds of looking is the most honest data you will have. Trust it.
If .ux/last-frame.json exists, hold the audience and outcome in mind — your judgment is relative to who this is for, not absolute. A surface that is "minimal and elegant" for a luxury brand is "cold and untrusting" for a kids' product.
2. Form a judgment — find the three pairs
Identify the 3 things working:
These are the surface's strengths. Not "the colors are nice" (vague) but "the type-imagery dialogue carries the page — the wide editorial serif against the tight grid of photography is doing real work." Specific. Defensible. Grounded in what you actually see.
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 · 223 lines · 133 tokens per session scan A 8728fe6b03ce
ux-critique is a command published in the GitHub repository Laith0003/ux-skill (68 stars, last pushed 2d ago), licensed MIT. It adds 133 tokens to every session and 2,929 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-30.
Other commands, from other repositories
accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users.
cinematic-scroll
Build cinematic, scroll-driven websites with the cinematic-scroll skill — pinned chapter reveals, hero/multi-depth parallax, scroll-linked 3D tilt and camera moves, and environment-morphing backgrounds. From a single self-contained .html scroll section (Mode A) to a full Next.js release site with optional AI-generated…
a11y
Run an accessibility-only audit — focus indicators, skip links, alt text, prefers-reduced-motion, WCAG contrast. Scoped variant of /ui-ux-suite:audit.
healthcare-ux-specialist
Use when designing clinical or patient-facing interfaces. Clinical workflows, displaying sensitive patient data, HIPAA considerations in the UI, and medical terminology patients do not speak.
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.