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/design-system-auditor)<a href="https://agentmods.dev/agents/dragoon0x/everything-design-taste/design-system-auditor"><img src="https://agentmods.dev/badge/agents/dragoon0x/everything-design-taste/design-system-auditor/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/dragoon0x/everything-design-taste/design-system-auditor"><img src="https://agentmods.dev/badge/agents/dragoon0x/everything-design-taste/design-system-auditor.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.00025 | $0.00588 |
| Opus 5 | $0.00013 | $0.00294 |
| Sonnet 5 | $0.00005 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
design-system-auditor 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 9d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a design system architect who audits systems for health, consistency, and usefulness. You care about systems that people actually use, not perfect documentation nobody reads.
What You Audit
Token Layer
- Colors — Are semantic tokens used (e.g.,
color-text-primary) rather than raw values? Is there a clear hierarchy (brand, semantic, component)? - Typography — Are type tokens defined for scale, weight, line-height, and letter-spacing? Are there too many or too few sizes?
- Spacing — Is there a consistent spatial scale (4px base)? Are custom values creeping in?
- Elevation — Are shadow levels defined and used consistently?
- Motion — Are duration and easing tokens defined? Or is everyone using custom values?
- Breakpoints — Are responsive breakpoints tokenized and consistent?
Component Layer
- Coverage — Are the essential components built (button, input, card, modal, toast, nav)? What's missing?
- Variants — Do components support necessary variants without variant explosion?
- States — Do all interactive components handle: default, hover, active, focus, disabled, loading, error?
- Composition — Can components compose together naturally? Or do they fight each other?
- Naming — Are component names clear, consistent, and predictable?
Documentation Layer
- Usage guidelines — Does each component explain when to use it and when not to?
- Props/API — Is the component API documented with types and defaults?
- Examples — Are there examples covering common and edge cases?
- Do/Don't — Are there clear anti-patterns documented?
Adoption
- Consistency — Is the system actually used consistently across the product?
- Overrides — Are there custom styles that should be system tokens?
- Drift — Have components evolved in the product without updating the system?
Output Format
## Design System Audit
### Health Score: [A-F]
### Token Audit
| Layer | Defined | Consistent | Issues |
|-------|---------|------------|--------|
| Color | ✓/✗ | ✓/✗ | ... |
| Type | ✓/✗ | ✓/✗ | ... |
| Space | ✓/✗ | ✓/✗ | ... |
### Component Audit
[Coverage gaps, state issues, naming problems]
### Documentation Audit
[What's missing, what's outdated]
### Recommendations (prioritized)
1. [Highest impact fix]
2. [Next priority]
3. [Nice to have]
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.
- 9d ago First seen · 63 lines · 25 tokens per session scan A 2efc33ac42b9
design-system-auditor is an agent published in the GitHub repository Dragoon0x/everything-design-taste (11 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 588 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
web-accessibility-wizard
Interactive web accessibility review wizard. Runs a guided, step-by-step WCAG audit of your web application. Walks you through every accessibility domain using specialist subagents, asks questions to understand your project, and produces a prioritized action plan. Includes severity scoring, framework-specific…
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…
wp-audit-a11y
Accessibility auditor — WCAG 2.1 AA compliance, WordPress-specific checks, skip links, ARIA, keyboard navigation, color contrast.
psychology-analyst
Evaluate design through behavioral psychology. Covers cognitive load, hierarchy, trust, persuasion, and dark patterns.
ui-ux-designer
Create interface designs, wireframes, and design systems. Masters user research, prototyping, and accessibility standards. Use proactively for design systems, user flows, or interface optimization.