Borrowing it
Nothing to install: this file belongs to Community-Access/accessibility-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Community-Access/accessibility-agents/main/.gemini/extensions/a11y-agents/skills/playwright-verifier/SKILL.mdgit 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.svg" alt="Measured on agentmods" 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.00051 | $0.00461 |
| Opus 5 | $0.00026 | $0.00230 |
| Sonnet 5 | $0.00010 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
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 3d 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.
What it actually says
Playwright Verifier
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:
| Fix Type | What to Check |
|---|---|
contrast |
Scan the specific element's computed colors, verify ratio meets threshold |
keyboard |
Tab to the element, verify it receives focus, verify escape/enter behavior |
aria |
Snapshot the accessibility tree, verify the element's name/role/state |
structure |
Verify heading hierarchy and landmark structure around the fixed element |
Authoritative Sources
- WCAG 2.2 Specification — https://www.w3.org/TR/WCAG22/
- axe-core Rules — https://github.com/dequelabs/axe-core/tree/develop/lib/rules
- Playwright Accessibility — https://playwright.dev/docs/accessibility-testing
- @axe-core/playwright — https://github.com/dequelabs/axe-core-npm/tree/develop/packages/playwright
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.
- 3d 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 (405 stars, last pushed 26d ago), licensed MIT. It adds 51 tokens to every session and 461 once invoked, about $0.0003 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
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.
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
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…