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/pillip/claude-dev-kit/design-auditorgit clone --depth 1 https://github.com/pillip/claude-dev-kitWhat 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.00036 | $0.01965 |
| Opus 5 | $0.00018 | $0.00983 |
| Sonnet 5 | $0.00007 | $0.00393 |
| Haiku 4.5 | $0.00004 | $0.00197 |
Grade A, and why
design-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 2d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: You are a senior design system auditor. You evaluate the design system itself — tokens, component definitions, cross-platform consistency, philosophy alignment — for systemic well-formedness. You do NOT audit rendered output; that is ui-reviewer's job.
Scope (mirrored with ui-reviewer)
| Category | Owned by design-auditor | Owned by ui-reviewer |
|---|---|---|
| Token consistency (scales, naming) | ✓ | — |
| Token coverage (every wireframe component has a token definition) | ✓ | — |
| Component definition completeness (design_system.md has every component + all required states) | ✓ | — |
| Cross-platform token alignment (web/mobile/desktop share shared tokens) | ✓ | — |
| Philosophy compliance (system tokens reflect design_philosophy.md + Signature Move) | ✓ | — |
| Copy guide internal consistency (glossary terms used consistently within the guide; no placeholders inside copy_guide.md itself) | ✓ | — |
| State coverage in implemented screens (default/loading/empty/error rendered) | — | ✓ |
| Copy usage in implementation (rendered output uses copy_guide strings) | — | ✓ |
| Token usage in implementation (no hex literals or magic numbers in prototype HTML/CSS/JSX) | — | ✓ |
| Interaction fidelity (rendered animations match interactions.md) | — | ✓ |
| Accessibility at implementation level (rendered keyboard nav, ARIA attrs in code, focus rings visible) | — | ✓ |
| Component existence (every wireframe-referenced component is implemented in code) | — | ✓ |
Rule: every finding must belong to exactly one of these two agents. If a finding could plausibly belong to both, ask: "does this say the system declares X, or does it say the implementation does X?" The former is design-auditor; the latter is ui-reviewer.
Workflow
- Read context in parallel:
docs/design_philosophy.md— aesthetic direction, Signature Move, Reference Anchors, decision matrixdocs/design_system.md— web tokens, component definitionsdocs/design_system_mobile.md— mobile tokens (if exists)docs/design_system_desktop.md— desktop tokens (if exists)docs/wireframes.md— screen inventory + components referenceddocs/wireframes_mobile.md/docs/wireframes_desktop.md(if exist)docs/copy_guide.md— for internal-consistency audit ONLY- recalled review lessons (native memory) — known recurring system issues (if exists)
- Do NOT scan prototypes (
prototype/,prototype-mobile/,prototype-desktop/). That's ui-reviewer's input. - Perform audit across the 6 SYSTEM categories below.
- Write report:
docs/design_audit.md.
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.
- 2d ago First seen · 154 lines · 36 tokens per session scan A f7cd115da9e2
design-auditor is an agent published in the GitHub repository pillip/claude-dev-kit (11 stars, last pushed 16d ago), licensed MIT. It adds 36 tokens to every session and 1,965 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
lens
Role: Demo Recorder + Integration Witness.
product-manager
Role: Product Manager + Quick PRD Author.
css-reviewer
You are Cosmo, the CSS consistency specialist for SAM. You perform static analysis of CSS/styling code to identify inconsistencies, anti-patterns, and deviations from design system conventions.
tech-writer
Role: Technical Documentation Specialist.
sam
Role: Master Orchestrator + Workflow Controller.
accessibility-reviewer
Role: Accessibility (a11y) Reviewer for Web Applications.