design-review

design-review is a command for Claude Code from nextlevelbuilder/ui-ux-pro-max-skill. It costs 0 tokens per session (174 once invoked), scanned A, original, MIT.

A command that reviews a web page in seven phases for accessibility, responsive behavior, and interaction quality.

In plain words
What is it for?
Use it on a page or URL to capture viewport screenshots, check WCAG AA accessibility requirements, and report findings from blockers to minor issues.
Why use it?
It finds and ranks design problems across screen sizes so serious issues can be fixed before the page is considered complete.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents; positional $N argument.

Part of the ui-ux-pro-max plugin — 7 skills, 2 commands, 1 agent shipped together

Good fit Use it on a page or URL to capture viewport screenshots, check WCAG AA accessibility requirements, and report findings from blockers to minor issues.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/nextlevelbuilder/ui-ux-pro-max-skill/design-review
About the project

UI UX Pro Max is an AI skill that supplies design guidance for creating user interfaces and user experiences across multiple platforms and frameworks. It is used by developers working with AI coding agents to plan and build application designs.

nextlevelbuilder/ui-ux-pro-max-skill · 136,581 stars · on GitHub · uupm.cc

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.

Clone the repo
git clone --depth 1 https://github.com/nextlevelbuilder/ui-ux-pro-max-skill

Made for: Claude Code.

Or install ui-ux-pro-max, the plugin that ships this one along with the rest of its 7 skills, 2 commands, 1 agent.

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-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/nextlevelbuilder/ui-ux-pro-max-skill/design-review/github.svg)](https://agentmods.dev/commands/nextlevelbuilder/ui-ux-pro-max-skill/design-review)
Your own site
<a href="https://agentmods.dev/commands/nextlevelbuilder/ui-ux-pro-max-skill/design-review"><img src="https://agentmods.dev/badge/commands/nextlevelbuilder/ui-ux-pro-max-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.

agentmods 80×15 button for design-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/nextlevelbuilder/ui-ux-pro-max-skill/design-review"><img src="https://agentmods.dev/badge/commands/nextlevelbuilder/ui-ux-pro-max-skill/design-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 174 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.00000 $0.00174
Opus 5.5 $0.00000 $0.00070
Sonnet 5.5 $0.00000 $0.00035
Haiku 4.5 $0.00000 $0.00017

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

Security

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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

stack/.claude/commands/design-review.md · 16 lines

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.

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. 1mo ago First seen · 16 lines · 0 tokens per session scan A df81f0c262ff

Subscribe to this mod's changes

design-review is a command published in the GitHub repository nextlevelbuilder/ui-ux-pro-max-skill (136,581 stars, last pushed 2d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.