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 tdimino/claude-code-minoan --skill design-auditgit clone --depth 1 https://github.com/tdimino/claude-code-minoanWrote 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/tdimino/claude-code-minoan/design-audit)<a href="https://agentmods.dev/skills/tdimino/claude-code-minoan/design-audit"><img src="https://agentmods.dev/badge/skills/tdimino/claude-code-minoan/design-audit/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/tdimino/claude-code-minoan/design-audit"><img src="https://agentmods.dev/badge/skills/tdimino/claude-code-minoan/design-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 13 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00068 | $0.01103 |
| Opus 5 | $0.00034 | $0.00551 |
| Sonnet 5 | $0.00014 | $0.00221 |
| Haiku 4.5 | $0.00007 | $0.00110 |
Grade A, and why
design-audit 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 10d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run systematic technical quality checks and generate a scored report. Don't fix issues — document them for other commands to address.
This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation.
Preparation
Read ~/.claude/skills/minoan-frontend-design/SKILL.md for anti-pattern guidance. Check .design-context.md for project context if it exists.
Read the ignore list at .design-critique/ignore.md if it exists. Findings matching an ignore entry (case-insensitive substring) should be silently dropped — the user has already acknowledged them as deferred tradeoffs or accepted deviations.
Diagnostic Scan
Check 5 dimensions. Score each 0-4 using ~/.claude/skills/minoan-frontend-design/references/heuristics-scoring.md criteria.
1. Accessibility
- Contrast ratios < 4.5:1 (or 7:1 for AAA)
- Missing ARIA: interactive elements without proper roles, labels, states
- Keyboard: missing focus indicators, illogical tab order, keyboard traps
- Semantic HTML: heading hierarchy, landmarks, divs-as-buttons
- Form issues: inputs without labels, poor error messaging
Score: 0=Inaccessible, 1=Major gaps, 2=Partial effort, 3=WCAG AA mostly met, 4=WCAG AA fully met
2. Performance
- Layout thrashing: reading/writing layout properties in loops
- Expensive animations: casual layout-property animation, unbounded blur/filter/shadow effects, or effects that visibly drop frames
- Missing optimization: no lazy loading, unoptimized assets, missing
will-change - Bundle size: unnecessary imports, unused dependencies
- Render performance: unnecessary re-renders, missing memoization
Score: 0=Severe issues, 1=Major problems, 2=Partial optimization, 3=Mostly optimized, 4=Fast and lean
3. Responsive Design
- Fixed widths that break on mobile
- Touch targets < 44x44px
- Horizontal scroll on narrow viewports
- Missing breakpoints or mobile variants
Score: 0=Desktop-only, 1=Major failures, 2=Works on mobile with rough edges, 3=Responsive with minor issues, 4=Fluid across all viewports
What ships with it
1 file 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.
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.
- 10d ago First seen · 103 lines · 68 tokens per session scan A bd6141c2c131
design-audit is a skill published in the GitHub repository tdimino/claude-code-minoan (41 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 1,103 once invoked, about $0.0003 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 skills, from other repositories
html-draft
Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on…
accessibility-testing
Audit web interfaces against WCAG 2.1 AA/AAA standards, identify violations, and produce actionable remediation reports with code fixes. Use when the user requests accessibility testing or provides relevant inputs for this workflow.
fec-component-testing
A guide for writing and reviewing front-end unit, component, and lightweight integration tests. These tests check small pieces of code and UI behavior without running a full browser journey.
fec-testing-strategy
A frontend testing strategy maps different risks to different checks, such as type checking, unit tests, component tests, integration tests, end-to-end tests, accessibility, security, and performance checks. It explains end-to-end testing as testing a complete user journey in a real browser.
fec-e2e-testing
A standard for real-browser end-to-end tests, which test complete user journeys across pages rather than isolated functions. It covers Playwright or Cypress, reusable page objects, test data, continuous-integration reports, screenshots, traces, videos, and unstable tests.
fec-tdd-workflow
A frontend test-driven development workflow, or TDD, describes the expected behavior with a failing test, implements the smallest change to pass it, and then refactors. It covers UI components, hooks, API clients, route guards, and user workflows.