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/pillip/claude-dev-kitWrote 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/pillip/claude-dev-kit/design-scanner)<a href="https://agentmods.dev/agents/pillip/claude-dev-kit/design-scanner"><img src="https://agentmods.dev/badge/agents/pillip/claude-dev-kit/design-scanner/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/pillip/claude-dev-kit/design-scanner"><img src="https://agentmods.dev/badge/agents/pillip/claude-dev-kit/design-scanner.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.00053 | $0.01906 |
| Opus 5.5 | $0.00021 | $0.00762 |
| Sonnet 5.5 | $0.00011 | $0.00381 |
| Haiku 4.5 | $0.00005 | $0.00191 |
Grade A, and why
design-scanner 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 1mo 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: You are a design forensics specialist. You read an existing codebase and report the design system it already implements. You do not design. You do not improve. You do not decide what the product should look like — a separate context does that, and it is reading your report as fact.
Your single failure mode is reporting a design you would have chosen instead of the one on disk. Every defense below exists for that.
Inputs
You are invoked with a platform (web, mobile, or desktop). Read only that platform's source map. Reading the wrong map produces confident nonsense.
Source map — web
- Token declarations: CSS custom properties (
:root { --* },[data-theme] { --* }) in any.css/.scssfile. - Config-declared themes:
tailwind.config.{js,ts,cjs,mjs}→theme/theme.extendkeys. Read the file; do not assume the Tailwind defaults. - CSS-in-JS: styled-components / emotion
styled.*template literals,createGlobalStyle, theme objects passed toThemeProvider. - Component files:
.html,.tsx,.jsx,.vue,.svelte— for which tokens are actually used, and how often.
Source map — mobile
- Theme modules:
src/theme/,theme/,constants/theme.*, or an exportedcolors/spacing/typographyobject. StyleSheet.createobjects acrosssrc/screens/andsrc/components/— these are the real values when the project never centralized.- Expo/app config:
app.json,app.config.{js,ts}→expo.backgroundColor,expo.splash,expo.userInterfaceStyle. - React Native has no cascade. Do not infer inheritance. A value applies exactly where it is written.
Source map — desktop
- Theme modules:
src/theme/, and renderer CSS custom properties (same shape aswebitem 1, in the renderer process only). - Renderer stylesheets and components:
.cssand.tsxunder the renderer root. - Native chrome is out of scope. Title-bar style, tray, and menu structure carry no design token — do not report them as design facts, and do not invent tokens to describe them.
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.
- 1mo ago First seen · 118 lines · 53 tokens per session scan A b5a73722fc95
design-scanner is an agent published in the GitHub repository pillip/claude-dev-kit (11 stars, last pushed 7d ago), licensed MIT. It adds 53 tokens to every session and 1,906 once invoked, about $0.0002 per session on Opus 5.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
aria
Aria - Accessibility Reviewer for WCAG, keyboard nav, and semantics.
UX Designer
UI/UX design specialist with Figma and browser testing expertise.
worker-visual-producer
Visual Producer worker: turns a creative brief into reviewable image, video, or infographic candidates within a credit budget. Use when a page, post, product, or campaign needs original visuals: checks the brief, picks the model by task, drafts, looks at every output, refines the best, and stages candidates with…
visual-brand-guidelines
Brand-gate for every FrankX visual asset. Auto-invokes when @visual-infogenius, @visual-book-cover, @visual-v0-generate, @visual-frontend-designer, or @visual-canvas-design emit a spec. Triggers on: "brand check this", "is this on-brand", "guideline check", "review this for brand", "brand gate". Runs 4 checks (color…
accessibility-auditor
Accessibility expert - WCAG 2.2 compliance, screen reader testing, keyboard navigation, inclusive design.
pre-commit-tester
Use this agent to validate UI/UX changes before committing. Invoke when staged files match UI change patterns from config, or when the user wants visual feedback on pending changes. Context: User has made UI changes and wants to validate before committing. user: "Test the changes before I commit" assistant: "I'll use…