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/dragoon0x/everything-design-taste/component-api-reviewergit 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-api-reviewer)<a href="https://agentmods.dev/agents/dragoon0x/everything-design-taste/component-api-reviewer"><img src="https://agentmods.dev/badge/agents/dragoon0x/everything-design-taste/component-api-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.00156 |
| Opus 5 | $0.00010 | $0.00078 |
| Sonnet 5 | $0.00004 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
component-api-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 6d 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 component API design.
What You Check
- Prop naming clarity and consistency.
- Default values (sensible defaults reduce configuration).
- Composition vs configuration approach.
- TypeScript types completeness.
- Ref forwarding support.
- Event handler naming (onX convention).
- Controlled vs uncontrolled patterns.
- Accessibility props (aria-label, role).
- Style override mechanism.
- Documentation quality.
Output: Component API Review
Naming Issues
DX Issues
Flexibility Issues
Recommendations
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.
- 6d ago First seen · 26 lines · 19 tokens per session scan A 4181e6f6e039
component-api-reviewer is an agent published in the GitHub repository Dragoon0x/everything-design-taste (11 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 156 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
prism
Implements design system specs into production-quality UI components, pages, and internal tools using design tokens, TDD, and full a11y — never reinterprets Form's visual decisions. Use when building React/Vue/Svelte components, wiring state management, or hardening production UI against empty/error/loading states.…
frontend-specialist
Frontend UI/UX implementation specialist.
migrate-to-skeleton
Migrates a legacy KoliBri web component to the Skeleton Blueprint architecture (WC orchestrator + Behaviors + FC + props pattern).
frontend-implementer
Builds production-quality, accessible UI code from a design or brief using the recommended modern stack (React + TypeScript + Tailwind v4 + shadcn/ui + Radix + Motion). Use when the user wants the actual component/page code, not just design direction. Produces clean, typed, accessible, state-complete components.
frontend-developer
Build React components, implement responsive layouts, and handle client-side state management. Masters React 19, Next.js 15, and modern frontend architecture. Optimizes performance and ensures accessibility. Use PROACTIVELY when creating UI components or fixing frontend issues.
react-security
PROACTIVELY review React code for security vulnerabilities, XSS risks, authentication issues, and React-specific security concerns. MUST BE USED when reviewing authentication, user input handling, API integration, or when explicitly requested for security review.