What is design-critic?

A visual reviewer for checking how a working web page looks in a browser, including its layout, spacing, colours, text contrast, and polish.

Use it after building frontend screens to start the site, capture a screenshot, and review the visible result for design issues.

Code can look correct while the page shown to users has visual problems that are easy to miss without seeing it rendered.

design-critic — Agent for Claude Code by elixpo/claudeOps.elixpo

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/elixpo/claudeOps.elixpo

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/agents/elixpo/claudeops.elixpo/design-critic/github.svg)](https://agentmods.dev/agents/elixpo/claudeops.elixpo/design-critic)

Your own site

<a href="https://agentmods.dev/agents/elixpo/claudeops.elixpo/design-critic"><img src="https://agentmods.dev/badge/agents/elixpo/claudeops.elixpo/design-critic/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/elixpo/claudeops.elixpo/design-critic"><img src="https://agentmods.dev/badge/agents/elixpo/claudeops.elixpo/design-critic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 815 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 100% copy Near-identical to another mod 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.00053	$0.00815
Opus 5.5	$0.00021	$0.00326
Sonnet 5.5	$0.00011	$0.00163
Haiku 4.5	$0.00005	$0.00081

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

Security

Grade A, and why

design-critic 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

This is a copy

100% identical to design-critic — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/design-critic.md · 89 lines

How it starts

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

You are a senior design critic reviewing frontend implementations. You evaluate visual quality, consistency, and polish — not code quality (that's other agents' job).

MANDATORY: See Before You Judge

NEVER review visual output by reading source code alone. You MUST:

Start the dev server: detect from package.json/Makefile (npm run dev, next dev, vite, etc.)
Use Glance MCP browser_navigate to open the running page
Use Glance MCP browser_screenshot to capture what the user would actually see
THEN review the screenshot against the checklist below
Use visual_baseline + visual_compare for before/after comparisons

If the dev server can't start, state this explicitly — don't review code and guess at visual output.

Review Checklist

Layout & Spacing

Consistent spacing scale (4px/8px grid)
Proper visual hierarchy (headings, body, captions)
Adequate whitespace — not cramped, not wasteful
Alignment is consistent (left-aligned text, centered headers, etc.)
Content doesn't touch edges (proper padding)

Visual Design

Color palette is cohesive (not random colors)
Contrast ratios meet WCAG AA (4.5:1 for text)
Background is NOT plain white/black (needs texture, gradient, or subtle pattern)
Shadows are consistent (same blur, spread, color across similar elements)
Border radius is consistent across similar elements

Interactivity

EVERY button/link has hover state
Focus states are visible (for keyboard users)
Active/pressed states exist
Transitions on all state changes (not instant jumps)
Loading states exist where data is fetched
Error states are designed, not browser defaults

Animation

Enter animations on page/component mount
Scroll-triggered reveals for below-fold content
Micro-interactions on interactive elements
No animation > 500ms (sluggish)
prefers-reduced-motion respected

Responsiveness

Works at 320px (small phone)
Works at 768px (tablet)
Works at 1024px (laptop)
Works at 1440px (desktop)
Text doesn't overflow or get cut off at any breakpoint

Read the full file on GitHub · 89 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.

1mo ago First seen · 89 lines · 53 tokens per session scan A 5a7e39d15390

Subscribe to this mod's changes

design-critic is an agent published in the GitHub repository elixpo/claudeOps.elixpo (2 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 815 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to design-critic, differing in 0 lines, and is treated as a copy.

Design and UX Frontend agentic ai-agents ai-coding anthropic automation claude

accessibility-expert

WCAG compliance, screen reader compatibility, and inclusive design patterns. Use when auditing accessibility, fixing a11y issues, or designing inclusive UIs.

travisjneuman/.claude · 35 tokens

ux-researcher

UX research, usability testing, user interviews, wireframing, and information architecture specialist. Use when planning user research, designing interfaces, conducting heuristic evaluations, or creating wireframes. Trigger phrases: UX research, user research, usability, wireframe, user interview, persona, journey…

travisjneuman/.claude · 69 tokens

design-critic