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 klovaaxel/web-a11y-agent-skills --skill web-a11y-cssgit clone --depth 1 https://github.com/klovaaxel/web-a11y-agent-skillsWrote 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/klovaaxel/web-a11y-agent-skills/web-a11y-css)<a href="https://agentmods.dev/skills/klovaaxel/web-a11y-agent-skills/web-a11y-css"><img src="https://agentmods.dev/badge/skills/klovaaxel/web-a11y-agent-skills/web-a11y-css/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/klovaaxel/web-a11y-agent-skills/web-a11y-css"><img src="https://agentmods.dev/badge/skills/klovaaxel/web-a11y-agent-skills/web-a11y-css.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.00048 | $0.00258 |
| Opus 5 | $0.00024 | $0.00129 |
| Sonnet 5 | $0.00010 | $0.00052 |
| Haiku 4.5 | $0.00005 | $0.00026 |
Grade A, and why
web-a11y-css 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.
What it actually says
Web A11y CSS
CSS Rules
- Do not remove focus indicators without a visible replacement.
- Do not rely on color alone for meaning.
- Respect reduced motion and provide user control for moving content.
- Preserve usability under zoom, reflow, large text, and forced-colors modes.
- Avoid CSS that breaks semantics or operability.
Risky CSS Checklist
CSS accessibility checklist
- [ ] Focus styles are visible and high contrast
- [ ] Text, controls, and states meet contrast expectations
- [ ] Target sizes and spacing support touch and motor constraints
- [ ] Motion is reduced or disabled when users request it
- [ ] `display`, `visibility`, `content-visibility`, and `pointer-events` do not break semantics
- [ ] Hidden labels, legends, captions, and referenced text still name controls correctly
Output
List preference modes tested, risky CSS properties used, and any semantic integrity mitigations.
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 First seen · 32 lines · 48 tokens per session scan A 717f97bf420a
web-a11y-css is a skill published in the GitHub repository klovaaxel/web-a11y-agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 258 once invoked, about $0.0002 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
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 Audit Helper
Reviews UI code and components for WCAG 2.1 accessibility violations and provides specific fixes.
a11y-planner
Use when you know what component, flow, or interface you need but not yet the right accessibility approach. Best for turning WCAG 2.2 requirements into an accessible implementation plan with WAI-ARIA APG patterns before code hardens bad interaction and state patterns.
color-contrast-auditor
Detects and fixes color contrast violations using WCAG 2.1 guidelines and perceptual analysis. Expert in contrast ratio calculation, color blindness simulation, and providing accessible alternatives. Activate on "check contrast", "color accessibility", "WCAG audit", "readability check", "contrast ratio", "hard to…
accessibility
Accessibility patterns for WCAG 2.2 compliance, keyboard focus management, React Aria component patterns, cognitive inclusion, native HTML-first philosophy, and user preference honoring. Use when implementing screen reader support, keyboard navigation, ARIA patterns, focus traps, accessible component libraries…
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.