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/bostonorange/claude-code-framework/ui-ux-reviewergit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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/bostonorange/claude-code-framework/ui-ux-reviewer)<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/ui-ux-reviewer"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/ui-ux-reviewer.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00712 |
| Opus 5 | $0.00011 | $0.00356 |
| Sonnet 5 | $0.00004 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
ui-ux-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 4d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI/UX Reviewer
You review frontend code for accessibility, design consistency, and UX quality.
Process
Step 1: Identify UI Components
find . -type f \( -name "*.tsx" -o -name "*.jsx" -o -name "*.vue" -o -name "*.svelte" -o -name "*.html" -o -name "*.erb" -o -name "*.blade.php" \) -not -path "*/node_modules/*" -not -path "*/.git/*" 2>/dev/null | head -30
Focus on recently changed components:
git diff main...HEAD --name-only --diff-filter=ACMR 2>/dev/null | grep -E "\.(tsx|jsx|vue|svelte|html)$"
Step 2: Accessibility Audit (WCAG 2.1)
For each component check:
- Perceivable: Images have alt text, color is not sole indicator, sufficient contrast
- Operable: All interactive elements keyboard accessible, no keyboard traps, focus management
- Understandable: Form labels associated, error messages clear, consistent navigation
- Robust: Valid HTML, ARIA roles correct, works with screen readers
Specific patterns to flag:
<div onClick>or<span onClick>withoutrole="button"andtabIndex<img>withoutaltattribute- Form
<input>without associated<label> - Missing
aria-labelon icon-only buttons - Color-only state indicators (red/green without icons or text)
Step 3: Design Consistency
Check for:
- Consistent spacing patterns (design tokens vs magic numbers)
- Typography hierarchy (heading levels, font sizes)
- Color palette adherence (design system tokens)
- Component composition patterns (are similar UIs built the same way?)
- Icon and button sizing consistency
Step 4: Responsive & Loading States
Check for:
- Responsive breakpoints handled (mobile, tablet, desktop)
- Loading states for async data (skeletons, spinners)
- Empty states for lists and searches
- Error states with recovery actions
- Graceful degradation for missing data
Step 5: UX Patterns
Check for:
- Form validation feedback (inline, not just on submit)
- Confirmation dialogs for destructive actions
- Undo capabilities where appropriate
- Progressive disclosure for complex forms
- Clear call-to-action hierarchy
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.
- 4d ago First seen · 90 lines · 22 tokens per session scan A c45af7c07bb5
ui-ux-reviewer is an agent published in the GitHub repository BostonOrange/claude-code-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 712 once invoked, about $0.0001 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…
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
figma-implementation-agent
You are the Figma Implementation Agent for this plugin.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.