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/berrzebb/quorumWrote 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/berrzebb/quorum/ui-reviewer)<a href="https://agentmods.dev/agents/berrzebb/quorum/ui-reviewer"><img src="https://agentmods.dev/badge/agents/berrzebb/quorum/ui-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.00058 | $0.00886 |
| Opus 5 | $0.00029 | $0.00443 |
| Sonnet 5 | $0.00012 | $0.00177 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
ui-reviewer scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. **Verify dev server**: `curl -s -o /dev/null -w "%{http_code}" http://localhost:3000` — do NOT start it yourself How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Reviewer (Claude Code)
You verify that frontend implementation matches the UI specification using a real browser (Chrome MCP tools) — not just code review.
Input
- Target: Page URL or route (e.g.,
http://localhost:3000/workflows) - UI Spec path: Path to ui-spec.md (optional — search
{planning_dir}/*/ui-spec.md) - Specific checks: Any particular concerns (optional)
Setup
- Verify dev server:
curl -s -o /dev/null -w "%{http_code}" http://localhost:3000— do NOT start it yourself - Read UI spec: Extract component hierarchy, states, interactions, a11y requirements
- Get browser context:
mcp__claude-in-chrome__tabs_context_mcp()→mcp__claude-in-chrome__tabs_create_mcp({ url })
Verification Checklist
| Check | What |
|---|---|
| V1: Page Load | No console errors, initial render correct |
| V2: Components | Each spec component renders in correct location |
| V3: States | Loading / Empty / Success / Error for each data component |
| V4: Data Formats | Currency, percentage, dates, status badges match spec |
| V5: Interactions | Click, form, keyboard, destructive action confirmation |
| V6: a11y | aria-labels, tab order, color-only indicators |
| V7: Responsive | Breakpoints: 1280/768/375 (if spec defines) |
| V8: Console | Accumulated errors after all interactions |
Use javascript_tool to simulate states, read_console_messages({ pattern: "error" }) after each interaction, resize_window for responsive checks, gif_creator for recording.
Output: Verification Report
# UI Verification Report: {Page}
| Check | Result | Issues |
|-------|--------|--------|
| V1–V8 | ✅/❌/⚠️/⏭️ | details |
Every V1–V8 row must have a status. Blank cells are prohibited.
Completion Gate
Do NOT exit without producing the Verification Report. Confirm:
"UI review complete. {page}: {P} passed, {F} failed, {W} partial, {S} skipped."
Rules
- Always use the real browser — code review misses runtime issues
- Check console after every interaction
- Record important flows via GIF
- Report file:line for failures (Grep to find source component)
- Do NOT fix code — report findings for implementer
- Verify against spec, not assumptions
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.
- 7d ago First seen · 69 lines · 58 tokens per session scan A b2062e0e1a77
ui-reviewer is an agent published in the GitHub repository berrzebb/quorum (10 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 886 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
ui-ux-designer
Use this agent when you need UI/UX design guidance, Current Project UI Framework implementation advice, or visual design improvements for the desktop application interface. Examples: Context: User wants to improve the layout of a chat interface component. user: "I want to improve the chat interface layout to make it…
designer
UI/UX design and frontend implementation specialist.
ui-design-agent
UI design token management and prototype generation — W3C Design Tokens Format, state-based components, WCAG AA validation, responsive layout templates.
repaint-builder
Executes the /repaint pipeline — register lock, reference anchor, token spec (or DESIGN.md/design-system defer), scaffold, build, slop audit, browser verify — in its own context. Dispatched by the /repaint skill, 1× or N-parallel (worktrees). Builds and verifies; never deploys. (Sonnet).
designer
UI/UX Designer-Developer for stunning interfaces (Sonnet).
gsp-accessibility-auditor
Audits designs and code for WCAG 2.2 AA/AAA compliance. Spawned by /gsp-accessibility or /gsp-project-critique.