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 pnakhat/qa-ai-repo --skill accessibility-testinggit clone --depth 1 https://github.com/pnakhat/qa-ai-repoWrote 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/pnakhat/qa-ai-repo/accessibility-testing)<a href="https://agentmods.dev/skills/pnakhat/qa-ai-repo/accessibility-testing"><img src="https://agentmods.dev/badge/skills/pnakhat/qa-ai-repo/accessibility-testing/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/pnakhat/qa-ai-repo/accessibility-testing"><img src="https://agentmods.dev/badge/skills/pnakhat/qa-ai-repo/accessibility-testing.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.00122 | $0.02391 |
| Opus 5 | $0.00061 | $0.01196 |
| Sonnet 5 | $0.00024 | $0.00478 |
| Haiku 4.5 | $0.00012 | $0.00239 |
Grade A, and why
accessibility-testing 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Testing
Make the UI usable by everyone — keyboard users, screen-reader users, low-vision users, people who need reduced motion. Automate what a machine can verify, then manually test what it can't. An axe pass is a floor, not a certificate.
Automation catches ~30–40% — the rest is manual
Automated tools reliably detect only about a third of real accessibility issues. The high-value bugs — a keyboard trap, a focus that vanishes, a button that reads as "button" with no name — are invisible to a scanner. Split the work honestly.
| ✅ Automation catches (cheap, gate it) | ❌ Needs a human (automation can't judge) |
|---|---|
Missing alt attribute on <img> |
Whether alt text is meaningful or noise |
| Color contrast below AA thresholds | Whether focus order is logical |
| Form control with no associated label | Whether an error message is understandable |
Duplicate id, invalid ARIA attribute |
Whether a custom widget is operable by keyboard |
Missing document lang, empty heading |
Whether a modal traps and restores focus |
Wrong role value, aria-* on wrong element |
Whether a screen reader announces state changes |
Missing name on a form field |
Whether the reading order matches the visual order |
Run axe on every key page/component to hold the line, then walk the manual checklist below for the flows that matter.
Automated setup — assert zero violations at the right level
Push a11y assertions as low as possible: unit/component where the markup lives,
one browser smoke for the assembled page. See reference.md for full code.
| Level | Tool | Use for |
|---|---|---|
| Component (unit) | jest-axe / vitest-axe (toHaveNoViolations) |
Design-system components, forms, widgets |
| Storybook | @storybook/addon-a11y + @axe-core/playwright on stories |
Every documented component state |
| E2E / page | @axe-core/playwright (AxeBuilder) as a fixture-level assertion |
Assembled pages, real routes, post-interaction states |
What ships with it
1 file 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.
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 · 163 lines · 122 tokens per session scan A 02620cc63108
accessibility-testing is a skill published in the GitHub repository pnakhat/qa-ai-repo (2 stars, last pushed 2mo ago), licensed MIT. It adds 122 tokens to every session and 2,391 once invoked, about $0.0006 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.