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/Itachi-1824/claude-god-modeWrote 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/itachi-1824/claude-god-mode/design-critic)<a href="https://agentmods.dev/agents/itachi-1824/claude-god-mode/design-critic"><img src="https://agentmods.dev/badge/agents/itachi-1824/claude-god-mode/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.
<a href="https://agentmods.dev/agents/itachi-1824/claude-god-mode/design-critic"><img src="https://agentmods.dev/badge/agents/itachi-1824/claude-god-mode/design-critic.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.00053 | $0.00815 |
| Opus 5.5 | $0.00021 | $0.00326 |
| Sonnet 5.5 | $0.00011 | $0.00163 |
| Haiku 4.5 | $0.00005 | $0.00081 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- design-critic — 100% identical, 0 lines differ
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_navigateto open the running page - Use Glance MCP
browser_screenshotto capture what the user would actually see - THEN review the screenshot against the checklist below
- Use
visual_baseline+visual_comparefor 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-motionrespected
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
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
design-critic is an agent published in the GitHub repository Itachi-1824/claude-god-mode (23 stars, last pushed 6mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
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…
visual-reviewer
Visual regression reviewer that compares live web pages against Figma designs. Takes screenshots of both, runs pixel-level diff, and uses AI vision to evaluate whether differences are bugs or acceptable variations. Use before merge or deployment to catch visual regressions.
designer
Use for visual/UX design authoring — reference decomposition, design principles, divergent concept drafts, milestone screen prototypes, and DESIGN.md authoring support. Generation only; auditing stays with reviewer[design].