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-dynamic-uigit 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-dynamic-ui)<a href="https://agentmods.dev/skills/klovaaxel/web-a11y-agent-skills/web-a11y-dynamic-ui"><img src="https://agentmods.dev/badge/skills/klovaaxel/web-a11y-agent-skills/web-a11y-dynamic-ui/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-dynamic-ui"><img src="https://agentmods.dev/badge/skills/klovaaxel/web-a11y-agent-skills/web-a11y-dynamic-ui.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.00245 |
| Opus 5 | $0.00024 | $0.00122 |
| Sonnet 5 | $0.00010 | $0.00049 |
| Haiku 4.5 | $0.00005 | $0.00024 |
Grade A, and why
web-a11y-dynamic-ui 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 Dynamic UI
Rules
- Client-side updates need non-visual feedback.
- Use live regions for status updates that should not move focus.
- Move focus only when it improves task flow and orientation.
- Use table semantics for tabular relationships, not layout.
- Communicate sort, current page, result count, and progress state semantically and visually.
Checklist
Dynamic UI checklist
- [ ] Active filters and result counts are discoverable
- [ ] Loading, empty, error, and success states are announced when needed
- [ ] Pagination exposes current page and available movement
- [ ] Progress indicators expose current step/value where meaningful
- [ ] Tables have captions or labels, headers, and sort state
- [ ] Interactive controls inside data views preserve context
Output
Document update announcement strategy, focus strategy, table/result semantics, and regression checks.
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 bad893433487
web-a11y-dynamic-ui 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 245 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.