design-review

design-review is a skill for Claude Code, Codex from event4u-app/agent-config. It costs 43 tokens per session (4,946 once invoked), scanned A, original, MIT.

A structured process for checking a user interface across usability, responsiveness, accessibility, interactions, and visual quality.

In plain words
What is it for?
It is for reviewing frontend changes, checking responsive behavior, testing user flows, and auditing interfaces against accessibility requirements.
Why use it?
It finds design problems that may be missed by reading code alone, such as layouts that break on smaller screens or interfaces that are difficult to use.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is [design-artifact verification checklist](../../../docs/contracts/design-artifact-verification.md#verification-checklist):.

Good fit It is for reviewing frontend changes, checking responsive behavior, testing user flows, and auditing interfaces against accessibility requirements.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/event4u-app/agent-config
agentmods
npx agentmods add skills/event4u-app/agent-config/design-review

Made for: Claude Code, Codex.

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/skills/event4u-app/agent-config/design-review/github.svg)](https://agentmods.dev/skills/event4u-app/agent-config/design-review)
Your own site
<a href="https://agentmods.dev/skills/event4u-app/agent-config/design-review"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/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/skills/event4u-app/agent-config/design-review"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/design-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,946 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 280
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
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.00043 $0.04946
Opus 5.5 $0.00017 $0.01978
Sonnet 5.5 $0.00009 $0.00989
Haiku 4.5 $0.00004 $0.00495

Measured 10d ago against content hash 489964fd5e32, 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 10d 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.

src/skills/design-review/SKILL.md · 401 lines

How it starts

The opening of the file, as written. The whole thing — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.

design-review

When to use

Render-verification gate. A UI verdict is gated on the design-artifact verification checklist: where render capability exists, do not pass a design task without render evidence (checklist steps 1–5); where it is absent, scope the verdict to what was statically checked and say so — never "looks good" without evidence.

Use this skill when:

  • Reviewing pull requests with UI changes
  • Auditing frontend components for design quality
  • Verifying responsive design across viewports
  • Checking accessibility compliance (WCAG 2.1 AA)
  • Testing interaction flows and user experience
  • Conducting visual QA on new features

Do NOT use when:

  • Creating new designs (use fe-design skill instead)
  • Reviewing backend/API code only
  • Quick syntax checks (use linters)

Prerequisites

One of the following browser automation tools:

  • Playwright MCP (recommended) — browser automation, screenshots, viewport testing
  • Chrome DevTools — screenshot capture, performance analysis

A live preview URL is required for testing.

Procedure: Design review

  1. Inspect the PR and preview — Read the PR description, diff, and identify changed components/pages; read the probe artifact and run the appearance floor over the preview URL (Phase 0).
  2. Walk the interactions — Run Phase 1; cover hover/focus/active/disabled, keyboard, loading, and form error states.
  3. Cover responsiveness, polish, a11y, robustness — Run Phases 2–5 in order; record findings per phase.
  4. Audit code-health and content — Run Phases 6–7; check tokens, dead styles, copy, console warnings.
  5. Verify and report — Consolidate findings in the report structure; classify each as Blocker / High / Medium / Nit before posting.

Phase 0: Preparation

  • Read PR description and git diff.
  • Identify changed components and affected pages.
  • Navigate to preview URL.
  • Read the probe artifact agents/runtime/state/ui-conformance.json (ui_conformance_probe --target <file> --reference <file>) — its per-dimension counters are the behavioral evidence Phases 1–2 report against. Absent is absent, never clean; a dimension the host could not exercise carries a not-applicable row with its reason rather than a zero.
  • Run the appearance floor (§ Appearance verification) — mandatory on every review.

Read the full file on GitHub · 401 lines

Files

What ships with it

4 files 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. 10d ago Changed · +1 lines 489964fd5e32
  2. 1mo ago Changed · +26 lines 442694a75361
  3. 1mo ago Changed · +50 lines 06fff58dbad5
  4. 2mo ago Changed · +2 tokens per session 138c44bfa972
  5. 2mo ago Changed · +2 lines dfade262de70
  6. 2mo ago First seen · 322 lines · 41 tokens per session scan A 00eebaf0b593

Subscribe to this mod's changes

design-review is a skill published in the GitHub repository event4u-app/agent-config (19 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 4,946 once invoked, about $0.0002 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-09-03.

Related

design-review compared with skills from other repositories

design-review next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
design-reviewevent4u-app/agent-configSkill19yesterdayMITA43Claude Code, Codex
huashu-designalchaincyf/huashu-designSkill29k2d agoMITA123Claude Code, Codex
gridkostja94/marketing-skillsSkill1.1k2d agoMITA29Claude Code, Codex
masonrykostja94/marketing-skillsSkill1.1k2d agoMITA32Claude Code, Codex
interaction-skillcode-yeongyu/oh-my-openagentSkill71kyesterdaynoneA104Claude Code, Codex
layout-skillcode-yeongyu/oh-my-openagentSkill71kyesterdaynoneA88Claude Code, Codex
ui-designer/html-prototypeechoVic/boss-skillSkill5475d agoMITA30Claude Code