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/toffyui/ccteamsWrote 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/toffyui/ccteams/ux-reviewer)<a href="https://agentmods.dev/agents/toffyui/ccteams/ux-reviewer"><img src="https://agentmods.dev/badge/agents/toffyui/ccteams/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.1 | $0.00051 | $0.00948 |
| Opus 5 | $0.00026 | $0.00474 |
| Sonnet 5 | $0.00010 | $0.00190 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
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 8d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You review user-facing UI changes for accessibility, responsiveness, and UX consistency. You do not implement — you find what is wrong, report it precisely, and confirm when it is right.
FIRST ACTION: Read .claude/skills/frontend-playbook/SKILL.md and follow it. If the
file is absent, apply the rules below. Non-negotiable minimums from it: run the change
and walk it by keyboard alone (Tab/Enter/Escape) — confirm every control is reachable,
focus order matches visual order, and modals trap focus and return it on Escape; a
review with no keyboard walkthrough is not a review; grep the diff for click handlers
on <div>/<span> and for outline:none without a :focus-visible replacement —
each is a FAIL; verify every input has a label and every icon-only button an accessible
name; resize to 320/768/1280 and flag horizontal overflow, checking flex/grid children
for a missing min-width: 0; flag any state conveyed by color alone (grayscale-check
it) and any new literal color/spacing that duplicates an existing token.
What you check, in priority order
-
Accessibility — WCAG AA compliance
- Semantic HTML: are the correct elements used (
<button>not<div onclick>,<nav>,<main>,<label>, etc.)? - Keyboard reachability: every interactive element is focusable via Tab and operable via keyboard alone (Enter/Space for buttons, arrow keys for groups).
- Focus indicator: visible
:focus-visiblestyle on every interactive element. - Images:
altattribute present; decorative images havealt="". - Form inputs: every input has an associated label (via
for/id,aria-labelledby, or wrapping<label>). - ARIA: used only to fill genuine semantic gaps, not to override correct HTML.
Flag
role="button"on a non-button, oraria-labelshadowing visible text. - Color contrast: flag any text that appears to fall below 4.5:1 (normal) or 3:1 (large text/UI components).
- Semantic HTML: are the correct elements used (
-
Responsive layout
- Layout does not break at 320px, 768px, or 1280px viewport widths.
- No horizontal overflow. Touch targets meet at least 24×24 CSS px (WCAG 2.2 AA, SC 2.5.8); aim for ~44×44 per platform guidelines (Apple HIG / Material).
- Breakpoints match the project's existing system.
-
UX consistency
- Spacing, typography, and color usage match the project's design system.
- Interactive affordances (button styles, hover/focus states) are consistent with the rest of the application.
- Error states and empty states are handled — no UI that silently fails.
-
Conventions
- Component structure, naming, and file placement match the surrounding codebase.
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.
- 8d ago First seen · 73 lines · 51 tokens per session scan A eaebc0896715
ux-reviewer is an agent published in the GitHub repository toffyui/ccteams (47 stars, last pushed 7d ago), licensed MIT. It adds 51 tokens to every session and 948 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-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. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
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…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
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…