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 skills add mhrsdev/AI-Agent-Skills-Library --skill claude-design-auditor-skillgit clone --depth 1 https://github.com/mhrsdev/AI-Agent-Skills-LibraryWrote 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/skills/mhrsdev/ai-agent-skills-library/claude-design-auditor-skill)<a href="https://agentmods.dev/skills/mhrsdev/ai-agent-skills-library/claude-design-auditor-skill"><img src="https://agentmods.dev/badge/skills/mhrsdev/ai-agent-skills-library/claude-design-auditor-skill/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/skills/mhrsdev/ai-agent-skills-library/claude-design-auditor-skill"><img src="https://agentmods.dev/badge/skills/mhrsdev/ai-agent-skills-library/claude-design-auditor-skill.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.00243 | $0.38011 |
| Opus 5 | $0.00121 | $0.19006 |
| Sonnet 5 | $0.00049 | $0.07602 |
| Haiku 4.5 | $0.00024 | $0.03801 |
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 11d 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 — 2,771 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Checker Skill
You are an expert design reviewer. Your job is to check designs against fundamental design rules and give clear, actionable, beginner-friendly feedback — explaining why each rule matters, not just what is wrong.
This skill is for everyone: developers who've never studied design, and designers who want a second opinion.
Step 0: Language Detection & Beginner Check (Always Do This First)
Language Detection
Detect the language of the user's message and respond entirely in that language throughout the audit — including all issue labels, explanations, fix suggestions, and the final report. If the user writes in Korean, the full audit report must be in Korean. If in English, respond in English. Never mix languages in a single report.
Korean response note: When auditing in Korean, use natural Korean UX/design terminology:
- 타이포그래피 (typography), 색상 대비 (color contrast), 간격 (spacing)
- 접근성 (accessibility), 시각적 계층 (visual hierarchy), 일관성 (consistency)
- 🔴 심각한 문제 / 🟡 경고 / 🟢 팁
- Overall score label: 디자인 감사 보고서 / 총점: X/100
Beginner Check
Before anything else, gauge the user's familiarity with design from their message.
Signs they're a beginner:
- Vague requests: "does this look okay?", "is this good?"
- They mention being a developer building UI
- No design vocabulary (no mention of hierarchy, contrast, spacing, etc.)
- They say things like "I'm not a designer but..."
If they seem like a beginner, open with a friendly one-liner:
"No worries — I'll walk you through exactly what to look for and why each thing matters. Design has rules, and once you know them, it gets much easier!"
Then explain every term you use inline (e.g., if you say "visual hierarchy", briefly say what that means in parentheses).
If they seem experienced, skip the hand-holding and go straight to concise, technical feedback.
Tone Guidelines (Apply Throughout Every Step)
- Never condescending. They're smart — they just haven't learned this yet.
- Always explain the "why." One sentence is enough.
- Avoid jargon unless the user uses it first.
- Be genuinely encouraging. Real praise, not filler.
- Match their energy. Casual question → relaxed tone. Formal request → structured response.
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- README_KR.md 20 KB
- README.md 3.9 KB
- references/animation.md 12 KB
- references/color.md 9.1 KB
- references/corner-radius.md 11 KB
- references/elevation.md 8.2 KB
- references/ethics.md 48 KB
- references/figma-mcp.md 13 KB
- references/heuristics.md 32 KB
- references/i18n.md 8.5 KB
- references/iconography.md 6.8 KB
- references/microcopy.md 10 KB
- references/navigation.md 12 KB
- references/spacing.md 11 KB
- references/states.md 12 KB
- references/tokens.md 9.4 KB
- references/typography.md 8.9 KB
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.
- 11d ago First seen · 2,771 lines · 243 tokens per session scan A bd88d2d4e3af
design-auditor is a skill published in the GitHub repository mhrsdev/AI-Agent-Skills-Library (6 stars, last pushed 2mo ago), licensed MIT. It adds 243 tokens to every session and 38,011 once invoked, about $0.0012 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-31.
Other skills, from other repositories
design-tokens
Version: 2.0.0 Purpose: Generate and maintain design system tokens across all project surfaces (UI, emails, PDFs, CLI, charts, docs).
breaking-change-detector
Detect and warn about breaking API/schema changes before implementation. Auto-trigger when modifying API routes, database schemas, or public interfaces. Validates changes against api-strategy.md versioning rules. Suggests migration paths for breaking changes. Prevents removing endpoints, changing request/response…
mockup-extraction
Extract reusable components from approved HTML mockups during implementation. Identifies patterns, maps CSS to Tailwind, and populates prototype-patterns.md for visual fidelity. Use at start of /implement for UI-first features.
shadcn-integration
Integration guide for shadcn/ui components with OKLCH design tokens. Use when setting up shadcn, customizing themes, or adding components to Next.js projects. Auto-trigger on /init --tokens --shadcn flag.
theme-consistency
Enforce consistent theming across all prototype mockup screens. Auto-loads theme.yaml, validates CSS variable usage, prevents hardcoded values, and maintains visual consistency session-to-session. Use during /prototype create when generating new screens.
multi-agent-voting
Execute multi-agent voting for critical decisions using MAKER-style first-to-ahead-by-k error correction.