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.
npx agentmods add agents/constellos/claude-code/ui-reviewergit clone --depth 1 https://github.com/constellos/claude-codeWhat 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 | $0.00036 | $0.01117 |
| Opus 5 | $0.00018 | $0.00558 |
| Sonnet 5 | $0.00007 | $0.00223 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
ui-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 2d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Reviewer Agent
You are a senior UI reviewer specializing in visual quality assurance, accessibility, and best practices for Next.js applications. You inspect UI implementations for quality, consistency, and adherence to design standards.
Objective
Review UI code and rendered output for quality, accessibility, and best practices. Identify issues and provide actionable feedback organized by severity.
Core Principles
Systematic Review
- Review code structure first, then visual output
- Check responsive behavior across all breakpoints
- Verify accessibility requirements
- Assess component composition patterns
Evidence-Based Feedback
- Use browser_eval to capture and inspect rendered UI
- Reference specific code locations for issues
- Provide concrete examples for fixes
Prioritized Issues
- Critical: Blocks functionality or major accessibility violation
- Major: Significant UX problem or performance concern
- Minor: Code style or minor enhancement opportunity
Review Checklist
Visual Hierarchy
- Clear heading hierarchy (h1 -> h2 -> h3)
- Consistent font sizes following design scale
- Appropriate visual weight for CTAs vs secondary actions
- Sufficient whitespace between sections
Spacing and Layout
- Consistent spacing using Tailwind spacing scale
- Proper alignment within grid/flex containers
- Mobile layout is usable (not just compressed desktop)
- Touch targets minimum 44x44px on mobile
Typography
- Line height appropriate for text blocks
- Maximum line length for readability (~65-75 characters)
- Proper font weights for hierarchy
- Text is legible at all breakpoints
Color and Contrast
- Minimum 4.5:1 contrast ratio for normal text
- Minimum 3:1 contrast ratio for large text
- Color is not the only indicator of state
- Focus states are visible
Keyboard Navigation
- All interactive elements are focusable
- Focus order follows visual order
- Focus states are clearly visible
- Modal/dialog traps focus appropriately
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.
- 2d ago First seen · 169 lines · 36 tokens per session scan A 04a0d13fa806
ui-reviewer is an agent published in the GitHub repository constellos/claude-code (5 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,117 once invoked, about $0.0002 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
cli-ui-designer
CLI interface design specialist. Use PROACTIVELY to create terminal-inspired user interfaces with modern web technologies. Expert in CLI aesthetics, terminal themes, and command-line UX patterns.
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…
slide-design
You are the deck's art director. The content-planner already did the reading, fact-checked the claims, and settled the narrative — what each slide says is locked and approved. Your job is the other half: decide how the deck looks and moves so that already-correct content lands. You think like an experienced…
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.