design-critique

design-critique is a skill for Claude Code from w2ur/claude-code-setup. It costs 36 tokens per session (2,515 once invoked), scanned A, original, MIT.

A review guide for checking how a web page actually looks in a browser. It uses captured evidence and a written set of criteria, then can either report issues or make one fix-and-check pass.

In plain words
What is it for?
Use it to audit or re-check a live site, local build, or recently changed page for visual and layout problems.
Why use it?
Reading code alone cannot show whether the browser rendered the intended design. It provides a bounded way to check the visible result instead of relying on a claim that the change is finished.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

Good fit Use it to audit or re-check a live site, local build, or recently changed page for visual and layout problems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/w2ur/claude-code-setup/design-critique
Install

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.

Any agent
npx skills add w2ur/claude-code-setup --skill design-critique
Clone the repo
git clone --depth 1 https://github.com/w2ur/claude-code-setup

Made for: Claude Code.

Wrote 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.

agentmods badge for design-critique

README.md
[![agentmods](https://agentmods.dev/badge/skills/w2ur/claude-code-setup/design-critique/github.svg)](https://agentmods.dev/skills/w2ur/claude-code-setup/design-critique)
Your own site
<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.

agentmods 80×15 button for design-critique

Your own site · 80×15
<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>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,515 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 6d ago against content hash f0ca0cf20cff, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

skills/design-critique/SKILL.md · 186 lines

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.

Read the full file on GitHub · 186 lines

Files

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.

Changes

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.

  1. 6d ago First seen · 186 lines · 36 tokens per session scan A f0ca0cf20cff

Subscribe to this mod's changes

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.