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 OneWave-AI/ClaudeCodeUnleashed --skill accessibility-auditorgit clone --depth 1 https://github.com/OneWave-AI/ClaudeCodeUnleashedWrote 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/onewave-ai/claudecodeunleashed/accessibility-auditor)<a href="https://agentmods.dev/skills/onewave-ai/claudecodeunleashed/accessibility-auditor"><img src="https://agentmods.dev/badge/skills/onewave-ai/claudecodeunleashed/accessibility-auditor.svg" alt="Measured on agentmods" 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.00033 | $0.01941 |
| Opus 5 | $0.00016 | $0.00971 |
| Sonnet 5 | $0.00007 | $0.00388 |
| Haiku 4.5 | $0.00003 | $0.00194 |
Grade A, and why
accessibility-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 6d 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Auditor
Instructions
When auditing accessibility:
- Run automated checks (axe, Lighthouse)
- Manual keyboard testing
- Screen reader testing
- Check WCAG criteria
- Provide fixes
Automated Testing
# Lighthouse accessibility audit
npx lighthouse https://yoursite.com --only-categories=accessibility --view
# axe-core CLI
npx @axe-core/cli https://yoursite.com
# Pa11y
npx pa11y https://yoursite.com
React Testing Library + jest-axe
import { render } from '@testing-library/react';
import { axe, toHaveNoViolations } from 'jest-axe';
expect.extend(toHaveNoViolations);
test('Button has no accessibility violations', async () => {
const { container } = render(<Button>Click me</Button>);
const results = await axe(container);
expect(results).toHaveNoViolations();
});
Playwright Accessibility Testing
import { test, expect } from '@playwright/test';
import AxeBuilder from '@axe-core/playwright';
test('page has no accessibility violations', async ({ page }) => {
await page.goto('/');
const results = await new AxeBuilder({ page }).analyze();
expect(results.violations).toEqual([]);
});
WCAG Checklist
Level A (Minimum)
Perceivable
- 1.1.1 Non-text content has alt text
- 1.3.1 Info and relationships are programmatically determined
- 1.3.2 Meaningful reading sequence
- 1.4.1 Color is not the only way to convey info
Operable
- 2.1.1 All functionality available via keyboard
- 2.1.2 No keyboard traps
- 2.4.1 Skip navigation link provided
- 2.4.2 Pages have descriptive titles
- 2.4.3 Focus order is logical
- 2.4.4 Link purpose is clear
Understandable
- 3.1.1 Page language is specified
- 3.2.1 Focus doesn't cause unexpected changes
- 3.3.1 Errors are identified and described
- 3.3.2 Labels or instructions provided
Robust
- 4.1.1 Valid HTML (no duplicate IDs, proper nesting)
- 4.1.2 Name, role, value for all UI components
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.
- 6d ago First seen · 300 lines · 33 tokens per session scan A 1f1af377479e
accessibility-auditor is a skill published in the GitHub repository OneWave-AI/ClaudeCodeUnleashed (5 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 1,941 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
compiler-review
Review Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.
add-session-recording
Add privacy-aware session recording and replay to React applications using the Temps SDK. Captures user interactions for playback while respecting privacy through input masking, element blocking, and GDPR-compliant consent flows. Use when the user wants to: (1) Add session recording to their app, (2) Implement session…
wcag
Expert WCAG (Web Content Accessibility Guidelines) advisor covering WCAG 2.0, 2.1, and 2.2 — the W3C international accessibility standards. Use this skill whenever a user asks about WCAG success criteria, conformance levels (A/AA/AAA), accessibility audits, POUR principles, accessibility statements, ARIA patterns…
accessibility-auditor
Audit web pages and components for WCAG 2.2 accessibility compliance. Use when a user asks to check accessibility, find a11y issues, audit for WCAG compliance, fix screen reader problems, check color contrast, ensure keyboard navigation works, or prepare for accessibility regulations like the European Accessibility…
wicked-garden-product-accessibility
Use when auditing code for WCAG 2.1 AA compliance — keyboard navigation, ARIA patterns, color contrast, and semantic HTML. Produces prioritized remediation with code-level fixes. NOT for running automated a11y tools (use product:a11y command) or visual design review (use product/visual-review).
accessibility-audit
Audit web pages and apps for WCAG 2.1 AA accessibility compliance. Use when fixing lighthouse issues, contrast ratios, ARIA labels, or keyboard navigation.