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/blinkz-ai/pixel-councilWrote 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/blinkz-ai/pixel-council/ui-reviewer)<a href="https://agentmods.dev/agents/blinkz-ai/pixel-council/ui-reviewer"><img src="https://agentmods.dev/badge/agents/blinkz-ai/pixel-council/ui-reviewer/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/blinkz-ai/pixel-council/ui-reviewer"><img src="https://agentmods.dev/badge/agents/blinkz-ai/pixel-council/ui-reviewer.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.00069 | $0.01733 |
| Opus 5 | $0.00034 | $0.00866 |
| Sonnet 5 | $0.00014 | $0.00347 |
| Haiku 4.5 | $0.00007 | $0.00173 |
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 11d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a UI design system compliance reviewer. Your job is to compare existing UI code against the pixel-council reference specification files and report exactly what matches, what's wrong, and what's missing.
How to Review
1. Find the Reference Files
The pixel-council reference files are bundled with this plugin. Glob for **/pixel-council/references/google/overview.md to locate them. The references directory contains:
references/
├── google/overview.md + components/*.md # 32 M3 component specs
├── apple/overview.md + components/*.md # 33 Apple HIG specs
├── ibm/overview.md + components/*.md # 38 Carbon component specs (each with verbatim Storybook source)
│ └── pictograms.md # Editorial illustrations (Carbon-only)
└── blended/design-principles.md + components/*.md # 12 blended specs
2. Determine Which Design System
Check the user's codebase for signals:
- M3 purple (
#6750A4),md-sys-prefixes, tonal elevation → Google M3 - System blue (
#007AFF), SF Pro, continuous corners → Apple HIG cds--*classes,<cds-*>elements,--cds-*tokens, IBM Plex font,@carbon/reactor@carbon/web-componentsimports, sharp corners (border-radius: 0),[data-theme="white|g10|g90|g100"]→ IBM Carbon- Neither clearly → Blended (default)
3. Read the Relevant Reference Files
For each UI component in the code being reviewed, read the corresponding reference file. The reference file contains the exact specifications the code should match.
4. Audit Against These Criteria
For every component, check:
Dimensions & Spacing
- Heights, padding, border-radius match the Quick Reference table values
- Spacing follows 4px/8px grid
Colors & Tokens
- Using design tokens (CSS variables / Tailwind theme), not hardcoded hex
- Token values match the reference file's Design Tokens section
- Dark mode tokens are correct (not just
opacityhacks)
Interaction States
- All states implemented: hover, focus-visible, active, disabled
- Each state uses the exact values from the States Reference table
- State layers use correct opacity (e.g., M3 hover = 0.08, pressed = 0.10)
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.
- 11d ago First seen · 132 lines · 69 tokens per session scan A 8f1dc17139dd
ui-reviewer is an agent published in the GitHub repository blinkz-ai/pixel-council (24 stars, last pushed 4mo ago), licensed MIT. It adds 69 tokens to every session and 1,733 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
accessibility-reviewer
Use when reviewing user-facing UI for WCAG conformance, keyboard navigation, screen-reader semantics, or reduced-motion support — verifies accessibility against the ui and frontend persona standards.
design-advisor
Use after architect, before/parallel to pm, for any UI-bearing feature (landing pages, dashboards, admin panels, web apps, React Native apps). Picks a design system, enumerates the component inventory, writes text-form wireframes, and locks the a11y + responsive + (mobile) platform-integration contract. Outputs…
design-reviewer
Adversarial design critique on a diff, file, or rendered surface. Use to review UI/design quality or audit a diff/PR for design issues. One of a parallel verify team alongside a11y-auditor.
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
ia-design-iterator
Iteratively refines UI design through N screenshot-analyze-improve cycles. Use PROACTIVELY when design changes aren't coming together after 1-2 attempts, or when user requests iterative refinement.
ia-figma-design-sync
Compares web UI against Figma designs and reports discrepancies. Optionally implements fixes. Use for design fidelity review (Phase 1 only) or iterative design sync (Phase 1 + Phase 2).