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/nicohodt/claude-code-ui-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/nicohodt/claude-code-ui-ux-skill/design-review)<a href="https://agentmods.dev/commands/nicohodt/claude-code-ui-ux-skill/design-review"><img src="https://agentmods.dev/badge/commands/nicohodt/claude-code-ui-ux-skill/design-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/nicohodt/claude-code-ui-ux-skill/design-review"><img src="https://agentmods.dev/badge/commands/nicohodt/claude-code-ui-ux-skill/design-review.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00174 |
| Opus 5.5 | $0.00000 | $0.00070 |
| Sonnet 5.5 | $0.00000 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
design-review 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 1mo 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.
This is a copy
100% identical to design-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Use the design-review subagent to audit the target below. Drive a real browser via the Playwright MCP, screenshot each viewport tier, and return ranked findings (Blockers → Nitpicks).
Target: $1 Focus (optional): $2
If no target was given, ask for the running dev-server URL (or a file path). If a browser
cannot be opened, fall back to node scripts/design-audit.mjs and report only the heuristic
findings, clearly labeled as such. Fix Blockers and High-severity findings before reporting the
work as complete.
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.
- 1mo ago First seen · 16 lines · 0 tokens per session scan A df81f0c262ff
design-review is a command published in the GitHub repository nicohodt/claude-code-ui-ux-skill (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 174 tokens. A static security scan graded it A with 0 findings. It is 100% identical to design-review, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
design-review
Run a UX/visual design audit of a URL using Antigravity (agy). Captures desktop + mobile screenshots, scores 10 dimensions (hierarchy, typography, color, spacing, a11y, etc.), benchmarks against industry. Saves to docs/agy/design-reviews/.
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
design-enforce
Use when code has drifted off the design system. Raw hex values and pixel numbers written where a token already exists, one-off components, library defaults left untouched. Finds every bypass and fixes it.
design-grill
Use when a design keeps getting reinvented every session. Interviews you until you share one understanding, then writes the vocabulary and the binding decisions into the repo so they survive the next context window.
design-triage
Use when a dwic audit report is full of findings and there is no plan. Ranks them into an order someone can work through, then works through it.
ccc-theme
List, preview or switch the Commander terminal color theme (Claude, OLED Black, Matrix, or a random palette) used by hooks and terminal art. Use when the user asks to change the theme, colors or skin.