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-orchestratorgit 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-orchestrator)<a href="https://agentmods.dev/skills/klovaaxel/web-a11y-agent-skills/web-a11y-orchestrator"><img src="https://agentmods.dev/badge/skills/klovaaxel/web-a11y-agent-skills/web-a11y-orchestrator/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-orchestrator"><img src="https://agentmods.dev/badge/skills/klovaaxel/web-a11y-agent-skills/web-a11y-orchestrator.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.00045 | $0.00584 |
| Opus 5 | $0.00023 | $0.00292 |
| Sonnet 5 | $0.00009 | $0.00117 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
web-a11y-orchestrator 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web A11y Orchestrator
Goal
Coordinate accessible UI work from scope discovery through implementation, review, remediation, and validation.
Routing Map
- New pages, app shells, semantic structure ->
web-a11y-authoring,web-a11y-navigation,web-a11y-css - Components, controls, overlays, custom interactions ->
web-a11y-authoring,web-a11y-css - Links, downloads, external destinations, images, SVG, media ->
web-a11y-authoring,web-a11y-testing - Forms, validation, search, multi-step flows ->
web-a11y-forms - Navigation, landmarks, breadcrumbs, skip links, menus ->
web-a11y-navigation - Filtering, sorting, pagination, live updates, tables ->
web-a11y-dynamic-ui - Styling, focus, contrast, motion, zoom, forced colors ->
web-a11y-css - Web components or Shadow DOM ->
web-a11y-web-components - Audits, triage, CI, DevTools, custom checks ->
web-a11y-debugging,web-a11y-review,web-a11y-testing
Workflow
A11y workflow
- [ ] Define scope and changed user journeys
- [ ] Select relevant skill passes from routing map
- [ ] Implement semantic-first UI
- [ ] Review for accessibility defects and missing tests
- [ ] Remediate Critical/High issues
- [ ] Validate with automation, keyboard, and screen reader smoke checks
Severity Policy
- Critical: blocks core task completion for keyboard or assistive technology users.
- High: creates major confusion, lost state, or unreliable operation.
- Medium: degrades usability but has a workable path.
- Low: polish, consistency, or non-blocking robustness improvement.
Public References
Use public references for deeper decisions:
- W3C WCAG
- WAI Tutorials
- WAI-ARIA Authoring Practices Guide
- MDN Web Docs
- WebAIM
- axe documentation and browser DevTools accessibility docs
Output
End with:
Accessibility report
Scope:
- <pages/components/journeys>
Passes run:
- <skills/checks>
Blocking issues:
- <severity> <issue> <status>
Verification:
- Automated: pass/fail/not run
- Keyboard: pass/fail/not run
- Screen reader smoke: pass/fail/not run
Decision:
- Ready | Needs remediation | Needs follow-up
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 · 79 lines · 45 tokens per session scan A 78ba7e69983b
web-a11y-orchestrator is a skill published in the GitHub repository klovaaxel/web-a11y-agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 584 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 A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
Axe-core Accessibility Testing
Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.
Accessibility Audit Helper
Reviews UI code and components for WCAG 2.1 accessibility violations and provides specific fixes.
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 Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
axe-core Accessibility Automation
Automated accessibility testing with axe-core integrated into CI pipelines, including custom rule configuration, issue prioritization, and remediation guidance.