A review command for checking accessibility and responsive behavior in a React or Next.js branch. Accessibility means making interfaces usable by people with disabilities, while responsive behavior means working across different screen sizes.

It reviews the whole branch or a selected path, feature, or base branch for WCAG 2.1 AA accessibility issues and layout problems across screen sizes.

It helps catch interface problems that can prevent people from using a site with assistive technology or on smaller screens.

review-a11y — Command for Claude Code by smicolon

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/smicolon/ai-kit

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/smicolon/ai-kit/review-a11y.svg)](https://agentmods.dev/commands/smicolon/ai-kit/review-a11y)

Your own site

<a href="https://agentmods.dev/commands/smicolon/ai-kit/review-a11y"><img src="https://agentmods.dev/badge/commands/smicolon/ai-kit/review-a11y.svg" alt="Measured on agentmods" height="20"></a>

Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,370 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.

Model	Per session	Once invoked
Fable 5.1	$0.00044	$0.01370
Opus 5	$0.00022	$0.00685
Sonnet 5	$0.00009	$0.00274
Haiku 4.5	$0.00004	$0.00137

Measured 5d ago against content hash 10a87c62e3be, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

review-a11y 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 5d 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.

packs/react-review/commands/review-a11y.md · 108 lines

How it starts

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

You are reviewing the current branch for accessibility (a11y) and responsive behavior ONLY. Ignore architecture and visual polish unless they directly cause an a11y or responsiveness issue.

Step 0 — Interpret the scope

User argument: $ARGUMENTS

Classify into one of four modes. The first two lines of your output MUST be:

Mode: <whole-branch | path: <p> | feature: <name> | base: <branch>>
Reviewed N files in scope. Found X P0, Y P1, Z P2 findings.

Mode A — Whole branch (empty): Review everything changed vs main.
Mode B — Path scope (contains / or a known extension, or matches git ls-files $ARGUMENTS): Review only changes inside that path.
Mode C — Feature scope (single bareword): Find files related via git ls-files | grep -i <feature>, intersect with branch diff.
Mode D — Base branch (matches a real branch): Review against that base instead of main.

Ambiguous → prefer branch if git branch -a confirms.

Step 1 — Scope the diff

Based on the mode:

A: git diff main...HEAD --stat
B: git diff main...HEAD --stat -- <path>
C: Compute the file list from the feature match, diff each relevant file.
D: git diff <base>...HEAD --stat

Also check for changes to global styles, layout primitives, or anything affecting breakpoints.

Step 2 — Evaluate each changed component

Accessibility

Semantic HTML — correct element used (button vs div, nav, main, section, proper heading levels)?
ARIA — used only when semantics are insufficient, and used correctly?
Keyboard navigation
- All interactive elements reachable by Tab?
- Focus order logical?
- Focus visible (no outline: none without replacement)?
- Escape closes modals/popovers, Enter/Space activates buttons?
Focus management — trapped in modals, restored on close, moved on route change (React Router / Next.js navigation)?
Labels — every input programmatically labeled (htmlFor + id), not just placeholder?
Color contrast — WCAG AA (4.5:1 body, 3:1 large text)?
Motion — respects prefers-reduced-motion?
Images — alt text meaningful, or empty for decorative? Next.js <Image> has alt?
Dynamic content — live regions (aria-live) for async updates where appropriate?
Icon-only buttons — have accessible names (aria-label or visually-hidden text)?

Read the full file on GitHub · 108 lines

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.

5d ago First seen · 108 lines · 44 tokens per session scan A 10a87c62e3be

Subscribe to this mod's changes

review-a11y is a command published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 1,370 once invoked, about $0.0002 per session on Opus 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.

Claude Code Design and UX Frontend ai ai-agent ai-agents ai-assistant claude

design-qa

Agent-driven design QA — walk the running app, judge design/UX, and drop a Comment-Mode comment on every issue (visible to the human as pins). Then read the session back and fix everything in bulk. Optional focus argument steers the pass.

DevZonayed/Mochi · 52 tokens

designer

UI/UX design with Memory coordination for consistent experiences.

airmcp-com/mcp-standards · 0 tokens

sddesign

Full spec-driven pipeline — walks brief → tokens → shape (spec) → craft (build) → converge → ship in one guided run. Writes .ui-craft/spec.md. Run when starting a net-new surface from scratch.

educlopez/ui-craft · 46 tokens

craft

One-shot build pipeline for a complete surface from an outcome recipe — inputs (or defaults) → composition → theme → build order → acceptance bar. Use when the user asks for a whole surface ("build me a dashboard", "I need a landing page") and expects a shippable result, not component-level help.

educlopez/ui-craft · 64 tokens

responsive-design-specialist

Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.

imsaif/design-with-claude · 36 tokens

spec-screenshot

Analyze website screenshots and generate detailed implementation specs.

sablier-labs/plugin-marketplace · 8 tokens