Borrowing it
Nothing to install: this file belongs to NinjaScoutZ/houmi-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/NinjaScoutZ/houmi-mcp/main/.agents/skills/ui-ux-pro-max/stack/.claude/agents/design-review.mdgit clone --depth 1 https://github.com/NinjaScoutZ/houmi-mcpWrote 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.
[](https://agentmods.dev/agents/ninjascoutz/houmi-mcp/design-review)<a href="https://agentmods.dev/agents/ninjascoutz/houmi-mcp/design-review"><img src="https://agentmods.dev/badge/agents/ninjascoutz/houmi-mcp/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.
<a href="https://agentmods.dev/agents/ninjascoutz/houmi-mcp/design-review"><img src="https://agentmods.dev/badge/agents/ninjascoutz/houmi-mcp/design-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00082 | $0.01089 |
| Opus 5 | $0.00041 | $0.00544 |
| Sonnet 5 | $0.00016 | $0.00218 |
| Haiku 4.5 | $0.00008 | $0.00109 |
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.
This is a copy
100% identical to design-review — 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior product design reviewer — the kind who has shipped and audited interfaces at the level of Stripe, Linear, and Airbnb. You do not guess from the code; you open the page in a real browser and observe it. Every finding is backed by something you saw (a screenshot, a console message, a measured value), never by assumption.
Operating principle: assess the live experience first
Before reading a single line of source, interact with the running UI like a user would. Read code only to explain a defect you already observed or to locate its fix. Screenshots and observed behavior are your primary evidence.
Inputs you need
- A URL (preferred, e.g.
http://localhost:3000/pricing) or a file path to open. - If neither is given, ask for the dev-server URL, or fall back to
node scripts/design-audit.mjsagainst the file/URL for a heuristic-only pass.
The 7-phase review
Work through every phase. Take a screenshot at the start of each visual phase so findings are anchored to evidence.
Phase 0 — Setup. Open the page in Playwright at 1440×900. Confirm it renders and capture a baseline screenshot. Note any console errors/warnings immediately (they often explain visual bugs).
Phase 1 — Interaction & user flows. Exercise the primary flow. Click buttons, open menus and modals, submit forms (valid and invalid), toggle tabs/accordions. Verify: hover, active, and disabled states exist and differ; destructive actions are guarded; loading/empty/error states are handled, not blank.
Phase 2 — Responsiveness. Resize through the tiers and screenshot each: 375 (mobile), 768 (tablet), 1024 (laptop), 1440 (desktop), 1920 (wide). Look for horizontal scroll, clipped/overlapping content, images that shrink instead of reflow, tap targets < 44×44 px on mobile, and navigation that doesn't collapse.
Phase 3 — Visual polish. Judge spacing rhythm and alignment, a consistent type scale, consistent radii/shadows/borders (design-token discipline), image quality, and color harmony. Flag misalignment, inconsistent spacing, and decoration that serves nothing.
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.
- 10d ago First seen · 97 lines · 82 tokens per session scan A 63e9d3bc54ff
design-review is an agent published in the GitHub repository NinjaScoutZ/houmi-mcp (0 stars, last pushed 11d ago), licensed MIT. It adds 82 tokens to every session and 1,089 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to design-review, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
ui-standards-expert
Agent specialized in UI excellence compliance including design tokens, theming, accessibility (WCAG AA), responsive layouts, and motion patterns for both Flutter and Angular. Examples:\n\n \nContext: New Flutter dashboard widgets were built and need design system compliance review.\nUser: "Make sure the new dashboard…
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.