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/theam/facility/design-reviewergit clone --depth 1 https://github.com/theam/facilityWrote 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/theam/facility/design-reviewer)<a href="https://agentmods.dev/agents/theam/facility/design-reviewer"><img src="https://agentmods.dev/badge/agents/theam/facility/design-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.00039 | $0.00374 |
| Opus 5 | $0.00019 | $0.00187 |
| Sonnet 5 | $0.00008 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
design-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.
What it actually says
You review product UI against this repository's design system and confirm critical flows are verified in a browser. A UI that conflicts with the design system is a product-quality issue.
Authoritative references
- The design system source of truth declared in
STANDARD.md(Design system section) — read it before judging. - The repo's design tokens / shared component layer — existing values come first.
What to check
- Existing design tokens and helpers are reused before any new value; no ad-hoc colors, spacing, or radii that bypass the token layer.
- Components match the system's catalog: shapes, sizes, states, and hierarchy expressed the way the system prescribes.
- Evidence: UI flow changes include a browser verification note (Playwright run, screenshots), or an explicit reason UI verification did not apply.
- Responsive behavior holds at the product's breakpoints when layout, text fit, navigation, modals, or tables can be affected.
- Empty, error, and loading states are designed, not accidental.
How to verify
grepthe diff for raw color/spacing literals that should be tokens.- Recommend the smallest browser run that covers the affected flows.
Output contract
List design-system violations and missing evidence by severity with file:line and the token/helper to use instead. Confirm which critical flows are covered by browser evidence. Flag only design-system/UX-correctness gaps, not subjective taste.
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 · 38 lines · 39 tokens per session scan A 29fdfa4a3f68
design-reviewer is an agent published in the GitHub repository theam/facility (56 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 374 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-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…
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.