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 gaia-react/gaia --skill a11y-fixesgit clone --depth 1 https://github.com/gaia-react/gaiaWrote 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/gaia-react/gaia/a11y-fixes)<a href="https://agentmods.dev/skills/gaia-react/gaia/a11y-fixes"><img src="https://agentmods.dev/badge/skills/gaia-react/gaia/a11y-fixes/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/gaia-react/gaia/a11y-fixes"><img src="https://agentmods.dev/badge/skills/gaia-react/gaia/a11y-fixes.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 Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00079 | $0.03100 |
| Opus 5.5 | $0.00032 | $0.01240 |
| Sonnet 5.5 | $0.00016 | $0.00620 |
| Haiku 4.5 | $0.00008 | $0.00310 |
Grade A, and why
a11y-fixes 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 12d 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Fix Patterns
Contents: Fix-then-verify loop; color-contrast; label; label-title-only; image-alt; button-name; link-name; region / landmark-one-main; heading-order; aria-allowed-attr; aria-required-attr; aria-required-children / aria-required-parent; aria-valid-attr-value; focus-trap (focus management); tabindex; html-has-lang; document-title; duplicate-id; listitem; definition-list; Upstream shadcn and Base UI findings.
Violations come from addon-a11y, which axe-checks every story under Vitest (configured in .storybook/a11y.ts), .playwright/a11y.ts (Playwright), or the code-audit-frontend agent's a11y bucket. General a11y guidance lives in frontend/.claude/rules/accessibility.md.
Fix-then-verify loop
- Fix one violation with the pattern below; for a rule id not listed here, use the violation's
helpandfailureSummaryfrom the axe output. - Re-run the reporter that flagged it: Vitest
pnpm test --run --project storybook <story-file>, Playwrightpnpm pw <spec-file>. - Some rules are not checked by the story run. addon-a11y runs the WCAG 2.0/2.1 A and AA tags and disables
region(a story renders a fragment outside the page landmarks), solandmark-one-mainandpage-has-heading-onenever fire there: assert the page landmark and heading in the page story's play instead (exactly onemain, one level-1 heading). Verifycolor-contrastwithpnpm pwwhen a story run is ambiguous, since the Playwright scan renders the same stories in the full page. - Repeat until the reporter shows no violations.
color-contrast
WCAG AA requires 4.5:1 for normal text, 3:1 for large text. Use the theme role tokens (see frontend/.claude/rules/tailwind.md) instead of raw palette colors: each token carries a light and a dark value that pass in both themes. Pair a surface token with its foreground (bg-primary with text-primary-foreground).
// BAD, fails contrast in dark mode, raw colors
<p className="text-gray-400 bg-white">Status</p>
// GOOD, role tokens, contrast-safe in both themes
<p className="bg-background text-foreground">Status</p>
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.
- 12d ago Changed · -2 lines 64360c79ee27
- 15d ago Changed 3797f4aca2ce
- 16d ago Changed · +2 lines 9b83b6add4d0
- 17d ago Changed · -9 lines 0030fe63712f
- 23d ago Changed · -94 tokens per session b8d36489283e
- 26d ago Changed · +16 lines · +2 tokens per session 89a70bf99fe1
- 27d ago Changed 47a519e618a1
- 28d ago Changed e8a35c763a35
- 1mo ago Changed · +27 lines dcb4dfd45bc8
- 1mo ago First seen · 305 lines · 171 tokens per session scan A 997e82e5cf72
a11y-fixes is a skill published in the GitHub repository gaia-react/gaia (26 stars, last pushed 6d ago), licensed MIT. It adds 79 tokens to every session and 3,100 once invoked, about $0.0003 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 skills, from other repositories
audit-accessibility
Unified accessibility auditing workflow across static analysis, runtime testing, ARIA patterns, keyboard navigation, and color contrast. Use this skill whenever the user mentions accessibility, a11y, WCAG, ARIA roles, axe tests, screen readers, focus management, keyboard navigation, color contrast, or wants to audit…
playwright-page-objects
Use when creating page objects or refactoring Playwright E2E tests for better maintainability with Page Object Model patterns.
authoring-tests
Write and run automated tests for Elements components including unit, accessibility, visual, SSR, and lighthouse tests. Use this skill whenever the user wants to write, create, update, or debug test files (.test.ts, .test.axe.ts, .test.visual.ts, .test.ssr.ts, .test.lighthouse.ts). Also trigger when the user asks…
test-building-blocks
Test building block catalog — typed patterns for Storybook play-function tests, Vitest hook tests, Vitest unit tests, MSW handlers, and test data fixtures. Read the relevant rule file before writing or modifying any test, handler, or fixture. Covers: deciding which kind of test to write, authoring a new test from…
testing
A guide for testing React components with React Testing Library and Vitest. It emphasizes checking interfaces through the way users find and interact with them.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.