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 vasilyu1983/AI-Agents-public --skill qa-testing-accessibilitygit clone --depth 1 https://github.com/vasilyu1983/AI-Agents-publicWrote 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/vasilyu1983/ai-agents-public/qa-testing-accessibility)<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/qa-testing-accessibility"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/qa-testing-accessibility/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/vasilyu1983/ai-agents-public/qa-testing-accessibility"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/qa-testing-accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 343 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00042 | $0.05367 |
| Opus 5 | $0.00021 | $0.02684 |
| Sonnet 5 | $0.00008 | $0.01073 |
| Haiku 4.5 | $0.00004 | $0.00537 |
Grade A, and why
qa-testing-accessibility 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 9d 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Testing (Accessibility)
Accessibility testing automation, CI gating, and audit methodology for web and mobile. Use this skill to decide what to automate, what requires manual testing, and how to build a sustainable accessibility quality gate.
Key distinction: software-ui-ux-design covers accessible design. This skill covers accessible testing — tooling, CI gates, screen reader protocols, and conformance evidence.
Quick Start
- Add axe-core to existing component or E2E tests to catch common detectable issues early.
- Establish a baseline before enabling blocking gates on legacy codebases.
- Set a team-defined CI policy: a common starter is block on critical/serious, warn on moderate, but tune it per product risk and remediation maturity.
- Plan manual audit for what automation cannot judge reliably: context, usability, cognitive load, and assistive-technology behavior.
- Run screen-reader verification on critical user flows before release.
Workflow
- Gather the target surfaces, WCAG scope, and platform constraints.
- Cover what automation can reliably detect first.
- Add manual keyboard and screen-reader checks for critical journeys.
- Turn findings into CI gates, remediation work, and verification evidence.
Inputs to Gather
- Target WCAG level: AA (default) or AAA (specific requirements)
- Platforms: web, iOS, Android, or combination
- Assistive technology requirements: screen readers, switch access, voice control
- Existing accessibility tooling and baseline violation count
- Regulatory requirements: ADA Title II (US state/local government — WCAG 2.1 AA technical standard, extended compliance dates), Section 508 (US federal ICT — WCAG 2.0 AA baseline), EN 301 549 (current: V3.2.1/WCAG 2.1; V4.1.1/WCAG 2.2 AA expected ~Oct 2026), European Accessibility Act (EAA) — see
## Regulatory Landscapefor corrected dates and scope; do not assume any single deadline applies to a private US business - Critical user flows that must be accessible
- Design system or component library status (tested vs untested)
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 353 B
- assets/template-accessibility-audit.md 3.7 KB
- assets/template-accessibility-ci-config.md 4.7 KB
- assets/template-screen-reader-checklist.md 3.8 KB
- data/sources.json 13 KB
- learnings.consolidated.md 600 B
- learnings.md 636 B
- references/automated-auditing.md 8.4 KB
- references/ci-accessibility-gates.md 7.9 KB
- references/cognitive-accessibility.md 11 KB
- references/eslint-jsx-a11y-integration.md 4.5 KB
- references/keyboard-navigation.md 7.0 KB
- references/mobile-accessibility.md 7.6 KB
- references/screen-reader-testing.md 8.8 KB
- references/wcag-automation-matrix.md 13 KB
- scripts/generate-a11y-baseline.ts 4.5 KB runs code
- scripts/README.md 2.6 KB
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.
- 9d ago First seen · 379 lines · 42 tokens per session scan A 398931c3b0d9
qa-testing-accessibility is a skill published in the GitHub repository vasilyu1983/AI-Agents-public (87 stars, last pushed 10d ago), licensed MIT. It adds 42 tokens to every session and 5,367 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-09-03.
Other skills, from other repositories
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
test-component
Write React Testing Library tests for an existing component, following the project's RTL conventions (prefer role/label queries, mock at network boundary, no act()). Invoke when the user asks to test, add tests for, or cover a component.
storybook
Storybook is the fidelity oracle, not the runtime. The converter bundles the package's compiled dist/ into dsbundle.js — the same bundle the claude.ai/design agent builds with — and generates each preview by compiling the story source module itself (hooks, fixtures, local helpers — the whole closure comes along), with…
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.