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/Dragoon0x/everything-design-tasteWrote 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/dragoon0x/everything-design-taste/component-reviewer)<a href="https://agentmods.dev/agents/dragoon0x/everything-design-taste/component-reviewer"><img src="https://agentmods.dev/badge/agents/dragoon0x/everything-design-taste/component-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.00019 | $0.00175 |
| Opus 5 | $0.00010 | $0.00088 |
| Sonnet 5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
component-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.
What it actually says
Component Reviewer
You evaluate component design for system health.
What You Check
- Component is reusable (not too specific, not too generic)
- API is consistent with existing components
- All necessary states handled
- Props are well-named and typed
- Component composes well with others
- Documentation is complete
- Accessibility requirements met
- Responsive behavior defined
Output
## Component Review: [Name]
### API Assessment
[Prop naming, defaults, typing]
### State Coverage
[Missing states]
### Consistency
[Alignment with existing system]
### Recommendations
[Improvements]
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 · 34 lines · 19 tokens per session scan A 44b5211740f3
component-reviewer is an agent published in the GitHub repository Dragoon0x/everything-design-taste (11 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 175 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-30.
Other agents, from other repositories
design-token-audit
Token-discipline sweep — greps source for raw color literals (hex / rgba / rgb / hsl, inline-style color props, Tailwind arbitrary color values) that bypass the design system, classifies each by severity (S0 chrome / S1 content / S2 internal / Exempt), and proposes the closest semantic token. Cheap, periodic…
design-reviewer
Use to audit UI code (SwiftUI, UIKit, AppKit, React/React Native, Flutter, HTML/CSS, etc.) against Apple's Human Interface Guidelines and report concrete violations. Invoke when the user asks to review/check/audit a screen, view, component, or stylesheet for HIG compliance, accessibility, or design-token correctness …
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.
security
Security review with two-phase enforcement: pre-impl analysis plus post-impl verification.
design-md-consumer
Load when the user's project ships a design contract — a .design file (schema design.v1) or a DESIGN.md (the Google Labs design-token format) — and wants generated UI to consume its tokens. Discovers the contract, resolves precedence, normalizes the tokens, and produces TypeScript / CSS variables / a Tailwind config /…
agentation-fix-loop
Load when the user is running an Agentation two-session workflow and you are the Session 2 (fix) side. Watches MCP annotations from the critique session, reads each annotation's selector + file path + critique, applies the fix in code, commits, and loops to the next. Use only when the agentation MCP server is…