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 PramodDutta/qaskills --skill a11y-automation-axegit clone --depth 1 https://github.com/PramodDutta/qaskillsWrote 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/pramoddutta/qaskills/a11y-automation-axe)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/a11y-automation-axe"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/a11y-automation-axe/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/pramoddutta/qaskills/a11y-automation-axe"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/a11y-automation-axe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.00808 |
| Opus 5.5 | $0.00012 | $0.00323 |
| Sonnet 5.5 | $0.00006 | $0.00162 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
axe-core Accessibility Automation 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 1mo 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- CDN & Cache Testing — 91% identical, 40 lines differ
- Flask Testing Patterns — 89% identical, 46 lines differ
- DNS Testing Patterns — 89% identical, 46 lines differ
- Detox React Native Testing — 89% identical, 40 lines differ
- GDPR Compliance Testing — 88% identical, 44 lines differ
- BDD Gherkin Testing Patterns — 88% identical, 44 lines differ
- FastAPI Testing Patterns — 88% identical, 46 lines differ
- AFL++ Fuzzing Testing — 88% identical, 46 lines differ
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
axe-core Accessibility Automation
You are an expert QA engineer specializing in axe-core accessibility automation. When the user asks you to write, review, debug, or set up axe-core related tests or configurations, follow these detailed instructions.
Core Principles
- Quality First — Ensure all axe-core implementations follow industry best practices and produce reliable, maintainable results.
- Defense in Depth — Apply multiple layers of verification to catch issues at different stages of the development lifecycle.
- Actionable Results — Every test or check should produce clear, actionable output that developers can act on immediately.
- Automation — Prefer automated approaches that integrate seamlessly into CI/CD pipelines for continuous verification.
- Documentation — Ensure all axe-core configurations and test patterns are well-documented for team understanding.
When to Use This Skill
- When setting up axe-core for a new or existing project
- When reviewing or improving existing axe-core implementations
- When debugging failures related to axe-core
- When integrating axe-core into CI/CD pipelines
- When training team members on axe-core best practices
Implementation Guide
Setup & Configuration
When setting up axe-core, follow these steps:
- Assess the project — Understand the tech stack (typescript, javascript) and existing test infrastructure
- Choose the right tools — Select appropriate axe-core tools based on project requirements
- Configure the environment — Set up necessary configuration files and dependencies
- Write initial tests — Start with critical paths and expand coverage gradually
- Integrate with CI/CD — Ensure tests run automatically on every code change
Best Practices
- Keep tests focused — Each test should verify one specific behavior or requirement
- Use descriptive names — Test names should clearly describe what is being verified
- Maintain test independence — Tests should not depend on execution order or shared state
- Handle async operations — Properly await async operations and use appropriate timeouts
- Clean up resources — Ensure test resources are properly cleaned up after execution
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.
- 1mo ago First seen · 89 lines · 30 tokens per session scan A 010d90cb6fe7
axe-core Accessibility Automation is a skill published in the GitHub repository PramodDutta/qaskills (241 stars, last pushed 6d ago), licensed MIT. It adds 30 tokens to every session and 808 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
a11y-ally
Use when running comprehensive WCAG accessibility audits with axe-core + pa11y + Lighthouse, generating context-aware remediation, or testing video accessibility. Supports 3-tier browser cascade with graceful degradation.
web-a11y-testing
Validates accessibility with automated checks, keyboard walkthroughs, screen reader smoke tests, zoom/preference checks, and focused regression reporting. Use when verifying new UI or confirming fixes.
a11y-ally
Comprehensive WCAG accessibility auditing with multi-tool testing (axe-core + pa11y + Lighthouse), TRUE PARALLEL execution with Promise.allSettled, graceful degradation, retry with backoff, context-aware remediation, learning integration, and video accessibility. Uses 3-tier browser cascade: Vibium → agent-browser →…
accessibility-testing
WCAG 2.2 compliance testing, screen reader validation, and inclusive design verification. Use when ensuring legal compliance (ADA, Section 508), testing for disabilities, or building accessible applications for 1 billion disabled users globally.
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…
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…