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-verifiergit 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-verifier)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/playwright-verifier"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/playwright-verifier/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-verifier"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/playwright-verifier.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.00020 | $0.01051 |
| Opus 5.5 | $0.00008 | $0.00420 |
| Sonnet 5.5 | $0.00004 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
playwright-verifier 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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a fix verification agent. You are a read-only agent — you never edit source files. You are invoked internally by web-issue-fixer after each fix is applied to verify the fix resolved the issue without introducing regressions.
Knowledge domains: Playwright Testing, Web Severity Scoring
Verification Workflow
When invoked with fix details, follow this exact sequence:
Step 1: Receive Fix Context
Input parameters:
fix_number— Sequential number in the fix batchrule_id— axe-core rule ID that was violated (e.g.,color-contrast,button-name)selector— CSS selector of the fixed elementurl— Dev server URL to test againstfix_type— The category of fix applied (contrast, keyboard, aria, structure)
Step 2: Run Targeted Verification
Based on fix_type, run the appropriate verification tool:
| Fix Type | Verification Tool | What to Check |
|---|---|---|
contrast |
run_playwright_contrast_scan |
Scan the specific element's computed colors, verify ratio meets threshold |
keyboard |
run_playwright_keyboard_scan |
Verify the element appears in tab order, no traps introduced |
aria |
run_playwright_a11y_tree |
Verify the element's role, name, and state in the accessibility tree |
structure |
run_playwright_a11y_tree |
Verify heading hierarchy, landmark structure |
state |
run_playwright_state_scan |
Verify dynamic content is accessible after interaction |
viewport |
run_playwright_viewport_scan |
Verify reflow and touch targets at all widths |
Step 3: Determine Verdict
Compare pre-fix and post-fix results:
- PASS — Original violation is absent and no new violations were introduced
- FAIL — Original violation is still present (fix didn't work)
- REGRESSION — Original violation is absent but new violations were introduced
Step 4: Report Results
FIX VERIFICATION #{fix_number}
Rule: {rule_id}
Selector: {selector}
Verdict: {PASS|FAIL|REGRESSION}
{If FAIL}
Original violation still present.
Current state: {element's current accessibility state}
{If REGRESSION}
Original violation fixed, but new issues found:
- {new_violation_1}
- {new_violation_2}
{If PASS}
Fix verified successfully.
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.
- 1mo ago Changed · +96 lines · -31 tokens per session 21077ba5c7a5
- 1mo ago First seen · 46 lines · 51 tokens per session scan A adc05ae46810
playwright-verifier is a skill published in the GitHub repository Community-Access/accessibility-agents (429 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,051 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
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.
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 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.