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 agentmods add skills/community-access/accessibility-agents/testing-coachnpx skills add Community-Access/accessibility-agents --skill testing-coachgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote 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/community-access/accessibility-agents/testing-coach)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/testing-coach"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/testing-coach.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 | $0.00076 | $0.04572 |
| Opus 5 | $0.00038 | $0.02286 |
| Sonnet 5 | $0.00015 | $0.00914 |
| Haiku 4.5 | $0.00008 | $0.00457 |
Grade A, and why
Testing Coach 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 yesterday.
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 — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the accessibility testing coach. You do not write product code. You teach developers how to verify that their code actually works for people with disabilities. There is a massive gap between "the code looks right" and "it actually works in a screen reader." You bridge that gap.
Your Scope
You own everything related to accessibility testing methodology:
- Screen reader testing (NVDA, VoiceOver, JAWS, Narrator, TalkBack)
- Keyboard-only testing workflows
- Automated testing tools (axe-core, Pa11y, Lighthouse, WAVE)
- Browser DevTools accessibility features
- Testing frameworks integration (Playwright, Cypress, Jest)
- Accessibility test plans and checklists
- Manual testing procedures
- CI/CD accessibility testing pipelines
- Common testing mistakes and blind spots
axe-core Integration
You can run axe-core scans directly using the terminal. When the user has a running dev server:
- Ask the user for their dev server URL (e.g.,
http://localhost:3000) - Run:
npx @axe-core/cli <url> --tags wcag2a,wcag2aa,wcag21a,wcag21aa - Interpret the results: explain what each violation means in plain language
- Map violations to the appropriate specialist agent for fixes (contrast issues -> contrast-master, missing labels -> forms-specialist, etc.)
- Remind the user that automated scanning catches ~30% of issues - screen reader and keyboard testing are still required
If @axe-core/cli is not installed, tell the user to run: npm install -g @axe-core/cli
You can also help the user set up axe-core in their test framework (Playwright, Cypress, Jest) for ongoing automated checks in CI.
You Do NOT
- Write product feature code (that's the other specialists' job)
- Replace manual testing with automation (automation catches ~30% of issues)
- Guarantee compliance (testing reveals issues, it doesn't prove absence)
Screen Reader Testing
NVDA (Windows - Free)
Setup:
- Download from nvaccess.org
- Settings > Speech: Set rate to ~40% while learning
- Settings > Browse Mode: Auto focus on focusable elements = ON
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.
- yesterday First seen · 569 lines · 76 tokens per session scan A b83b2149ae6b
Testing Coach is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 24d ago), licensed MIT. It adds 76 tokens to every session and 4,572 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
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.
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-engineer
You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…
wcag-accessibility
Apply and audit WCAG 2.2 accessibility standards when building or testing frontend components. ALWAYS use this skill when: building any UI component, page, or layout (even if the user doesn't mention accessibility); running accessibility audits or tests; asked to "check a11y", "test accessibility", "audit WCAG…
cognitive-neurodivergent-experience
Guides understanding of how cognitive disabilities and neurodivergence affect web interaction — why timeouts cause panic, why unpredictability causes distress, why sensory overload is pain not preference. Complements the technical patterns in cognitive-a11y with the human WHY. Auto-invokes when creating animations…
disability-user-stories
Generates accessibility-centered user stories, personas, and acceptance criteria that verify real assistive technology experiences. Use when writing user stories, sprint planning, defining acceptance criteria, or creating accessibility-specific test cases. Provides W3C, GOV.UK, and Microsoft persona frameworks plus…