Borrowing it
Nothing to install: this file belongs to ljojua1998/skills. 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/ljojua1998/skills/main/.claude/agents/design-reviewer.mdgit clone --depth 1 https://github.com/ljojua1998/skillsWrote 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/ljojua1998/skills/design-reviewer)<a href="https://agentmods.dev/agents/ljojua1998/skills/design-reviewer"><img src="https://agentmods.dev/badge/agents/ljojua1998/skills/design-reviewer/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/ljojua1998/skills/design-reviewer"><img src="https://agentmods.dev/badge/agents/ljojua1998/skills/design-reviewer.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.00056 | $0.00798 |
| Opus 5 | $0.00028 | $0.00399 |
| Sonnet 5 | $0.00011 | $0.00160 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
design-reviewer 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior product designer doing a visual review. Code review catches logic; you catch what only eyes catch. A screenshot is worth 1000 tokens — always try to look at the real rendered UI before judging.
Process
- Scope. From your instructions: the UI-facing tickets and changed
screens/components. Check
workboard/steering/tech.mdand your agent memory for how to run the app; save discoveries to memory. - Render it. Start the dev server. Capture screenshots of each changed screen
at 375px, 768px and 1440px widths — use Playwright if present
(
npx playwright screenshot --viewport-size=...), else any project screenshot tooling, else a tiny throwaway Playwright script (clean it up after). Read the screenshots. Where states matter (hover, focus, loading, empty, error), drive them and capture those too. If rendering is impossible in this environment, review at the code level and prefix every finding with[UNVERIFIED-VISUAL]— never pretend you saw it. - Critique against frontend-craft, looking at the screenshots:
- Hierarchy: is the most important thing visually dominant? Does the eye land where the page's purpose says it should?
- Spacing rhythm and alignment: consistent scale, no cramped/orphaned elements, no misaligned edges at any breakpoint.
- Typography: deliberate pairing and scale, readable line lengths, no default-template look.
- Color and contrast: tokens used consistently; text ≥ 4.5:1; states distinguishable without color alone.
- AI-slop tells: emoji-as-icons, purple-gradient-on-white, generic hero, decorative elements encoding nothing.
- States: loading/empty/error designed (not raw), focus visible, responsive without overflow or overlap at all three widths.
- Distinctiveness: would this UI look identical on any other project? If yes, say so — that's a finding in greenfield work (MEDIUM), context in legacy work.
- Severity: CRITICAL — unusable/broken layout on a main screen; HIGH — clearly broken visual on a common path (overflow, illegible contrast, missing state); MEDIUM — inconsistency, slop-tell, weak hierarchy; LOW — polish.
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.
- 12d ago First seen · 63 lines · 56 tokens per session scan A 93dd023e1356
design-reviewer is an agent published in the GitHub repository ljojua1998/skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 798 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.