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 skills add w2ur/claude-code-setup --skill design-critiquegit clone --depth 1 https://github.com/w2ur/claude-code-setupWrote 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/skills/w2ur/claude-code-setup/design-critique)<a href="https://agentmods.dev/skills/w2ur/claude-code-setup/design-critique"><img src="https://agentmods.dev/badge/skills/w2ur/claude-code-setup/design-critique/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/skills/w2ur/claude-code-setup/design-critique"><img src="https://agentmods.dev/badge/skills/w2ur/claude-code-setup/design-critique.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.00036 | $0.02515 |
| Opus 5.5 | $0.00014 | $0.01006 |
| Sonnet 5.5 | $0.00007 | $0.00503 |
| Haiku 4.5 | $0.00004 | $0.00251 |
Grade A, and why
design-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 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.
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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design critique — a rendered, bounded review loop
Code review cannot see a page. This skill reviews what the browser actually drew: screenshots and a deterministic detector first, judgment against a written rubric second, and a fix loop that stops after one re-check.
Two modes. Audit: report only, change nothing. Fix: the same review, then step 6. The caller says which; when unsaid, it is audit.
1. Evidence first
Evidence already captured. When the caller says the evidence is already in
<dir> with a design-detect exit code N (the design-audit command does,
after its sequential capture), do not run the script: <dir> is <outdir>
and N is the exit code read below — N = 2 still means unknown. Otherwise:
~/.claude/scripts/design-detect.sh <url|file> <outdir>
The script is the source of truth for its widths and the detector version — do
not restate them. Exit 0 = captured, no detector hit; 1 = captured, hits;
2 = unknown (capture failed, blank or error page, detector crashed). On
2, write unknown and the script's stderr (the caller's saved stderr file,
when the evidence was already captured) as the whole report, and stop: a page
that was not captured is never "clean".
In <outdir>, for each width and scheme the script captured:
shots/<width>-<scheme>-fold.png (first screen) and shots/<width>-<scheme>.png
(full page); then shots/1440-light-focus.png (keyboard focus), one
detect-<width>.json per detect width, capture.json (including the HTTP
status and hasDarkScheme) and console.json (console errors and uncaught
page errors during the load). A local file target yields one detect file —
say so; do not invent the other widths.
2. Context — what the project sanctions
Read the project's root DESIGN.md, and the design section or design entries of
its CLAUDE.md, and every design document either of them names — the hub's
CLAUDE.md points to design-and-themes.md (in its wrp-architecture skill)
for the rules its identity still obeys. List what they sanction, mapped to
detector ids, before looking at any finding. Reference case: the hub
(~/Dev/{portfolio-site}) documents its ground in the CLAUDE.md entry
"Deliberate identity: the paper palette", so cream-palette is sanctioned
there — and per design-tells A0, the companions it did not ask for (italic
accent word, terracotta, numbered eyebrows) are still findings.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 186 lines · 36 tokens per session scan A f0ca0cf20cff
design-critique is a skill published in the GitHub repository w2ur/claude-code-setup (2 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 2,515 once invoked, about $0.0001 per session on Opus 5.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-10-10.
Other skills, from other repositories
figma-design
Design, build, or edit a Figma file through a design connector (plugin-API calls verified with screenshots). Use whenever the task is to create or change a Figma design, mock up a UI, logo, infographic, or design system, build styles or components, or hand a design to dev. Triggers even if the user does not name Figma…
options
Present multiple design options as a vertical stack of anchored turns.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
archify
Validated interactive HTML diagrams, upstream-maintained.
ux-design
Section-by-section UX spec authoring for a screen, flow or HUD. Reads the player journey to provide context; also project-wide accessibility.
infographics
Create professional infographics using Nano Banana Pro AI with smart iterative refinement. Uses Gemini 3 Pro for quality review. Integrates research-lookup and web search for accurate data. Supports 10 infographic types, 8 industry styles, and colorblind-safe palettes.