Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ImYourBoyRoy/Portable_Web_toolkitnpx agentmods add skills/imyourboyroy/portable_web_toolkit/wcag-auditorWrote 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/imyourboyroy/portable_web_toolkit/wcag-auditor)<a href="https://agentmods.dev/skills/imyourboyroy/portable_web_toolkit/wcag-auditor"><img src="https://agentmods.dev/badge/skills/imyourboyroy/portable_web_toolkit/wcag-auditor.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.00072 | $0.00761 |
| Opus 5 | $0.00036 | $0.00380 |
| Sonnet 5 | $0.00014 | $0.00152 |
| Haiku 4.5 | $0.00007 | $0.00076 |
Grade A, and why
wcag-auditor 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 6d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WCAG Auditor
Use only Web_Toolkit/wcag_auditor (never AI/wcag-auditor or sibling trees).
Evidence gate only — not a WCAG conformance certificate.
Prerequisites
- Client project has a linked
Web_Toolkit/and*.site-profile.json. - Playwright peers in the client project (
playwright,@axe-core/playwright). - Chromium browser binary (
npx playwright install chromium). The CLI auto-installs these unless--skip-playwright-install.
Preferred commands
# With site profile (ephemeral config if no wcag-auditor.config.mjs)
node ./Web_Toolkit/wcag_auditor/bin/wcag-auditor.mjs run \
--site-profile ./<site>.site-profile.json \
--base-url https://example.com
# Persist a checked-in config
node ./Web_Toolkit/wcag_auditor/bin/wcag-auditor.mjs init --site-profile ./<site>.site-profile.json
node ./Web_Toolkit/wcag_auditor/bin/wcag-auditor.mjs run --site-profile ./<site>.site-profile.json --base-url http://127.0.0.1:4321
Confirm: node ./Web_Toolkit/wcag_auditor/bin/wcag-auditor.mjs core-path must end with Web_Toolkit/wcag_auditor.
After every run — share the dashboard
- Locate
wcag-audit-dashboard.htmlunder the run output directory (CLI printsstakeholder dashboard → …). - Open it and share the path with the user (Cursor canvas is optional extra; the HTML dashboard is the durable artifact).
- Prefer findings that show
file:line— those are best-effort maps from selectors/classes intosrc/. Unmapped rows still list the CSS selector for search. - JSON/SARIF remain for tools; dashboard is for humans.
Rules
- Pass
--site-profilefor toolkit sites. - Prefer live URL or local preview
--base-url; do not invent routes. - Fix findings with smallest safe CSS/markup changes; re-run after fixes.
- Do not treat PageSpeed Accessibility scores as WCAG proof.
- Always surface the stakeholder dashboard path in the chat reply after a run.
- Glassmorphism / frost UI is supported. Axe
color-contrastincompletes map tocantTell(exit 3 unresolved), not an auto-fail. Do not strip frost UI solely to silence the gate. Prefer: raise frost opacity / solid underlay under text → verify AA with a contrast sampler → completefrost-glass-contrastinwcag-audit/manual-evidence.json→ add a bounded suppression withoutcomes: ["cantTell"]foraxe/color-contraston the route. SeeWeb_Toolkit/wcag_auditor/docs/GLASSMORPHISM.md. - Never set
gate.unresolvedEvidence: "ignore"just to ship glass; resolve evidence properly.
What ships with it
2 files 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.
- 6d ago First seen · 49 lines · 72 tokens per session scan A 7c41e438c491
wcag-auditor is a skill published in the GitHub repository ImYourBoyRoy/Portable_Web_toolkit (2 stars, last pushed 25d ago), licensed MIT. It adds 72 tokens to every session and 761 once invoked, about $0.0004 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
write-frontend-tests
Analyze the current branch diff against dev, plan integration tests for changed frontend pages/components, and write them. TRIGGER when user asks to write frontend tests, add test coverage, or 'write tests for my changes'.
visual-qa
Rigorous visual QA for any UI you built or changed, across BOTH web/page UIs and TUI/terminal UIs. MUST USE after building or changing any UI to verify it visually before declaring it done. Captures objective reference evidence with a bundled diff script (image-diff for screenshots, tui-check for terminal captures)…
accessibility-tester
Professional Accessibility Tester Expert skill. Implement robust test suites and automated quality checks for modern web/mobile applications.
playwright-component-testing
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.
astro
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.