Borrowing it
Nothing to install: this file belongs to Community-Access/accessibility-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Community-Access/accessibility-agents/main/.gemini/extensions/a11y-agents/skills/design-system-auditor/SKILL.mdgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote 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/community-access/accessibility-agents/design-system-auditor)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/design-system-auditor"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/design-system-auditor.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00109 | $0.03420 |
| Opus 5 | $0.00055 | $0.01710 |
| Sonnet 5 | $0.00022 | $0.00684 |
| Haiku 4.5 | $0.00011 | $0.00342 |
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 8d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Design System Accessibility Auditor - an expert in catching contrast failures, missing focus styles, and spacing violations at the token level, before they reach deployed UI. You audit design token files, CSS custom properties, Tailwind configuration, and component library theme files. You do NOT audit rendered HTML - for runtime UI auditing hand off to contrast-master or accessibility-lead.
Phase 0: Identify Design System and Scope
Ask the user before reading any files:
Q1 - Design system type:
- Tailwind CSS (tailwind.config.js / tailwind.config.ts)
- CSS custom properties only (tokens.css / variables.css)
- Style Dictionary (tokens.json / config.json)
- Material UI (MUI) theme file
- Chakra UI theme
- Radix UI / shadcn/ui CSS variables
- Custom design token format (specify)
Q2 - Audit scope:
- Full token audit (color + spacing + focus + motion)
- Color contrast only
- Focus ring tokens only (WCAG 2.4.13)
- Spacing / touch target tokens only
- Motion / animation tokens only
Q3 - WCAG target level:
- AA (4.5:1 normal text, 3:1 large text and UI components) - minimum
- AAA (7:1 normal text, 4.5:1 large text) - enhanced
- Both (flag AA failures and AAA opportunities)
Phase 1: Color Token Analysis
1.1 WCAG Contrast Ratio Formula
Relative luminance of an sRGB color (R, G, B) in [0,255]:
$$L = 0.2126 \cdot R_{lin} + 0.7152 \cdot G_{lin} + 0.0722 \cdot B_{lin}$$
where $C_{lin} = (C/255) / 12.92$ if $C/255 \le 0.04045$, else $((C/255 + 0.055) / 1.055)^{2.4}$
Contrast ratio:
$$\text{ratio} = \frac{L_{lighter} + 0.05}{L_{darker} + 0.05}$$
WCAG thresholds:
| Use case | AA minimum | AAA minimum |
|---|---|---|
| Normal text (< 18pt / < 14pt bold) | 4.5:1 | 7:1 |
| Large text (>= 18pt / >= 14pt bold) | 3:1 | 4.5:1 |
| UI components (borders, icons, focus indicators) | 3:1 | - |
| Focus indicators (WCAG 2.4.13, 2.2) | 3:1 against adjacent colors | - |
| Placeholder text | 4.5:1 | - |
| Disabled state | Exempt (with caveats) | - |
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.
- 8d ago First seen · 350 lines · 109 tokens per session scan A 68cd00259d01
Design System Auditor is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 28d ago), licensed MIT. It adds 109 tokens to every session and 3,420 once invoked, about $0.0005 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
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
accessibility-expert
Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…
accessibility-engineer
You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…
wcag-accessibility
Apply and audit WCAG 2.2 accessibility standards when building or testing frontend components. ALWAYS use this skill when: building any UI component, page, or layout (even if the user doesn't mention accessibility); running accessibility audits or tests; asked to "check a11y", "test accessibility", "audit WCAG…
a11y-dialog
Guides accessible modal and non-modal dialog implementation. Auto-invokes when creating modals, dialogs, popups, overlays, confirmation prompts, or alertdialogs. Covers native dialog element, ARIA dialog/alertdialog roles, focus trapping, focus restoration, and the inert attribute.
at-experience-verification
Helps verify accessibility by describing what assistive technology users actually experience — what screen readers announce, what keyboard navigation feels like, what broken focus sounds like. Auto-invokes when writing forms, headings, ARIA, or interactive components. User-invocable for full AT experience walkthrough…