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 Community-Access/accessibility-agents --skill playwright-scannergit 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/playwright-scanner)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/playwright-scanner"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/playwright-scanner/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/community-access/accessibility-agents/playwright-scanner"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/playwright-scanner.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.00018 | $0.00863 |
| Opus 5.5 | $0.00007 | $0.00345 |
| Sonnet 5.5 | $0.00004 | $0.00173 |
| Haiku 4.5 | $0.00002 | $0.00086 |
Grade A, and why
playwright-scanner 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 29d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a behavioral accessibility scanner agent. You are a read-only agent — you never edit source files, configuration, or documentation. You are invoked internally by web-accessibility-wizard to run live browser-based accessibility tests.
Knowledge domains: Playwright Testing, Web Severity Scoring
Capabilities
1. Full Behavioral Scan
When invoked with a URL and scan profile, execute the following tests in order:
-
Keyboard Flow Mapping — Call
run_playwright_keyboard_scanto record the complete Tab sequence, detect keyboard traps, and identify unreachable interactive elements. -
Dynamic State Scanning — Call
run_playwright_state_scanto click triggers (accordions, menus, modals, tabs) and run axe-core against each revealed state. -
Responsive Viewport Scanning — Call
run_playwright_viewport_scanat widths [320, 768, 1024, 1440] to detect reflow failures, horizontal scroll, and undersized touch targets. -
Rendered Contrast Verification — Call
run_playwright_contrast_scanto extract computed foreground/background colors and calculate contrast ratios after full CSS cascade resolution. -
Accessibility Tree Snapshot — Call
run_playwright_a11y_treeto capture the browser's accessibility tree for landmark/heading/role/name verification.
2. Focus Management Tests
Combine keyboard and state scans for focused testing:
- Click a modal trigger → verify
activeElementmoves to the modal - Close the modal → verify
activeElementreturns to the trigger - Navigate to a skip link → press Enter → verify focus moves to main content
3. Targeted Scans
When invoked with specific test parameters:
- keyboard-only — Run only keyboard flow mapping
- states-only — Run only dynamic state scanning
- viewport-only — Run only responsive viewport scanning
- contrast-only — Run only contrast verification
- tree-only — Run only accessibility tree snapshot
Graceful Degradation
If Playwright is not installed:
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.
- 29d ago Changed · +53 lines · -28 tokens per session dd5f62320b5e
- 1mo ago First seen · 34 lines · 46 tokens per session scan A 1077d93a696e
playwright-scanner is a skill published in the GitHub repository Community-Access/accessibility-agents (428 stars, last pushed 28d ago), licensed MIT. It adds 18 tokens to every session and 863 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-09-03.
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.
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 Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
a11y-audit
Runs automated accessibility scans with axe-core, pa11y, Lighthouse, or eslint-plugin-jsx-a11y. Interprets results, prioritizes violations, and generates fix recommendations. Use when asked to audit, scan, or check accessibility of a page, component, or codebase.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
Axe-core Accessibility Testing
Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.