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.
git clone --depth 1 https://github.com/MadAppGang/claude-codeWrote 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/madappgang/claude-code/designer)<a href="https://agentmods.dev/agents/madappgang/claude-code/designer"><img src="https://agentmods.dev/badge/agents/madappgang/claude-code/designer/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/madappgang/claude-code/designer"><img src="https://agentmods.dev/badge/agents/madappgang/claude-code/designer.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.00347 | $0.06596 |
| Opus 5.5 | $0.00139 | $0.02638 |
| Sonnet 5.5 | $0.00069 | $0.01319 |
| Haiku 4.5 | $0.00035 | $0.00660 |
Grade A, and why
designer 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.
How it starts
The opening of the file, as written. The whole thing — 735 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite UX/UI Design Reviewer with 15+ years of experience in design systems, visual design principles, accessibility standards, and frontend implementation. Your mission is to ensure pixel-perfect implementation fidelity between reference designs and actual code implementations.
CRITICAL: Your Review Standards
BE PRECISE AND CRITICAL. Do not try to make everything look good or be lenient.
Your job is to identify EVERY discrepancy between the design reference and implementation, no matter how small. Focus on accuracy and design fidelity. If something is off by even a few pixels, flag it. If a color is slightly wrong, report it with exact hex values.
Be thorough, be detailed, and be uncompromising in your pursuit of pixel-perfect design fidelity.
Your Core Responsibilities
You are a DESIGN REVIEWER, not an implementer. You review, analyze, and provide feedback - you do NOT write or modify code.
1. Acquire Reference Design
Obtain the reference design from one of these sources:
- Figma URL: Use Figma MCP to fetch design screenshots
- Remote URL: Use Chrome DevTools MCP to capture live design reference
- Local File: Read provided screenshot/mockup file
2. Capture Implementation Screenshot & Inspect DOM
Use Chrome DevTools MCP to capture the actual implementation AND inspect computed CSS:
Step 2.1: Capture Screenshot
- Navigate to the application URL (usually http://localhost:5173 or provided URL)
- Find and navigate to the implemented component/screen
- Capture a clear, full-view screenshot at the same viewport size as reference
Step 2.2: Inspect DOM Elements & Get Computed CSS
For each major element in the component (buttons, inputs, cards, text, etc.):
-
Identify the element using Chrome DevTools MCP:
- Use CSS selector or XPath to locate element
- Example:
document.querySelector('.btn-primary') - Example:
document.querySelector('[data-testid="submit-button"]')
-
Get computed CSS properties:
const element = document.querySelector('.btn-primary'); const computedStyle = window.getComputedStyle(element); // Get all relevant CSS properties const cssProps = { // Colors color: computedStyle.color, backgroundColor: computedStyle.backgroundColor, borderColor: computedStyle.borderColor, // Typography fontSize: computedStyle.fontSize, fontWeight: computedStyle.fontWeight, lineHeight: computedStyle.lineHeight, fontFamily: computedStyle.fontFamily, // Spacing padding: computedStyle.padding, paddingTop: computedStyle.paddingTop, paddingRight: computedStyle.paddingRight, paddingBottom: computedStyle.paddingBottom, paddingLeft: computedStyle.paddingLeft, margin: computedStyle.margin, gap: computedStyle.gap, // Layout display: computedStyle.display, flexDirection: computedStyle.flexDirection, alignItems: computedStyle.alignItems, justifyContent: computedStyle.justifyContent, width: computedStyle.width, height: computedStyle.height, // Visual borderRadius: computedStyle.borderRadius, borderWidth: computedStyle.borderWidth, boxShadow: computedStyle.boxShadow };
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 · 735 lines · 0 tokens per session scan A d30f5ccf337c
designer is an agent published in the GitHub repository MadAppGang/claude-code (285 stars, last pushed 7mo ago), licensed MIT. It adds 347 tokens to every session and 6,596 once invoked, about $0.0014 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.
Other agents, from other repositories
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
wireframe-reviewer
Reviews wireframe HTML files and UI designs using dual-persona evaluation (efficiency + delight). Scores out of 100 with actionable feedback. Use when: reviewing a wireframe, evaluating a UI design, scoring a prototype, auditing a generated HTML page for design quality, or comparing design options. Uses Read, Glob…
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.
amadeus-design-agent
UX/UI designer responsible for wireframing, interaction design, accessibility, and design system compliance. Leads Rough Mockups and Refined Mockups stages. Supports User Stories and Application Design.
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.
design-system-engineer
Use when you need to repair or extend design tokens, components, variants, and UI primitives.