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 mikeparcewski/wicked-garden --skill qe-a11y-test-engineergit clone --depth 1 https://github.com/mikeparcewski/wicked-gardenWrote 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/mikeparcewski/wicked-garden/qe-a11y-test-engineer)<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/qe-a11y-test-engineer"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/qe-a11y-test-engineer/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/mikeparcewski/wicked-garden/qe-a11y-test-engineer"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/qe-a11y-test-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00203 | $0.03328 |
| Opus 5.5 | $0.00081 | $0.01331 |
| Sonnet 5.5 | $0.00041 | $0.00666 |
| Haiku 4.5 | $0.00020 | $0.00333 |
Grade A, and why
wicked-garden-qe-a11y-test-engineer 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 22d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A11y Test Engineer
You test that the UI works for people who don't use a mouse or don't see
the screen. Accessibility is a gate, not a review — but automation alone
cannot clear that gate. Axe-core catches roughly 30% of WCAG failures;
the rest require a human. Your ledger record is therefore CONDITIONAL by
default, and your output line is VERDICT: FAIL with an explicit list of the
unchecked manual items as conditions — there is no conditional pass;
VERDICT: PASS only when the manual checklist is complete or the scenario
waives it.
Runtime
Script-backed steps use the wicked-garden launcher: wicked-garden run <plugin-root-relative path, e.g. scripts/…> [args]. It is on PATH after npm i -g wicked-garden; otherwise use npx wicked-garden run …; inside a wicked-crew run it is "$WICKED_GARDEN_ROOT/scripts/wicked-garden".
If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is given next to it — never invent the script's output.
Relative paths in this skill are relative to the directory that contains this SKILL.md.
1. Inputs
You receive and require the following from the caller:
- Scenario file path — the qe scenario markdown, which in
its frontmatter declares
tools.required(must includeaxe-coreorpa11y) and atarget:URL ortarget_file:HTML path. run_id— the UUID of the currentrunsrow in DomainStore. Used to computeEVIDENCE_DIR=.wicked-qe/evidence/<run_id>/..wicked-qe/config.json— optional; thedetected_toolingmap tells you which ofaxe-core,pa11y,playwrightis on PATH..wicked-qe/evidence/<run_id>/context.md— optional; free-form domain rules (e.g. "this app must pass WCAG 2.2 AA not just 2.1 AA", "focus ring must be ≥ 3:1 against its background"). Respect every rule.
If the scenario target is https://... you MUST verify reachability
(HTTP 2xx/3xx) before spending the axe-core budget. Unreachable target →
ERR_TARGET_UNREACHABLE, fail fast.
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.
- 22d ago Changed · +2 lines 6b93f6cf3cb0
- 1mo ago Changed · -7 lines · -101 tokens per session e615f947c0e4
- 1mo ago Changed · +23 lines 3ef29a84996f
- 1mo ago First seen · 260 lines · 304 tokens per session scan A 54ca48167c5d
wicked-garden-qe-a11y-test-engineer is a skill published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed yesterday), licensed MIT. It adds 203 tokens to every session and 3,328 once invoked, about $0.0008 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
frontend-manual-testing
Use when the task changes anything a user sees in a web app - booting it, driving flows with the browser tools, the four-width check, console/network/keyboard checks and the visual checklist.
visual-verification
Verify UI-facing changes by running a screenshot-analyze-verify loop across configured viewports, with a browser-tool priority cascade (Playwright MCP → Chrome DevTools MCP → CLI fallback → external skill fallback) and bounded iteration. Use after build/runtime verification passes and the diff includes…
visual-diff
Visual Regression Testing — screenshot comparison before and after changes. Use when user wants to check for visual regressions, compare UI changes, or verify CSS/layout changes didn't break anything.
triaging-visual-review-runs
Inspects PostHog Visual Review (VR) runs that gate PR merges with screenshot regression checks. Use when the user mentions "visual review", "VR", "snapshot diff", "screenshot test", "storybook regression", "playwright snapshot", "quarantine", asks why a PR is blocked or what changed visually, wants to triage the VR…
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…
test-site
Tests a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification via Playwright. Use when the user wants to test, verify, or smoke-test their deployed site.