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 accessibilitygit 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/accessibility)<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/accessibility"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/accessibility/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/accessibility"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/accessibility.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.00072 | $0.01781 |
| Opus 5 | $0.00036 | $0.00890 |
| Sonnet 5 | $0.00014 | $0.00356 |
| Haiku 4.5 | $0.00007 | $0.00178 |
Grade A, and why
wicked-garden-product-accessibility 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 5d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Skill
WCAG 2.1 Level AA compliance auditing and inclusive design guidance.
Core Principle
Accessibility is not optional. It's legal compliance, user respect, and better code.
WCAG 2.1 Four Principles: POUR
1. Perceivable
Information must be presentable to users in ways they can perceive.
- Text alternatives for images
- Color contrast 4.5:1 (normal), 3:1 (large)
- No info by color alone
2. Operable
Interface components must be operable.
- All functionality via keyboard
- No keyboard traps
- Visible focus indicators
3. Understandable
Information and operation must be understandable.
- Form labels associated
- Error messages clear
- Consistent navigation
4. Robust
Content must work with assistive technologies.
- Valid HTML (no duplicate IDs)
- Proper ARIA usage
- Status messages announced
Full WCAG checklists: See refs/wcag-checklist.md
Quick Audit Process
1. Automated Scan
Use the Read tool on a screenshot file, or capture via browser automation if available (e.g., Playwright, Puppeteer, or an MCP browser tool). For automated WCAG scanning, use axe DevTools, Lighthouse, WAVE, or pa11y.
2. Keyboard Test (5 minutes)
- Tab through entire page
- Can reach all interactive elements?
- Focus always visible?
- Tab order logical?
- Can escape modals/menus?
Full keyboard testing guide: See refs/keyboard-testing-basics.md and refs/keyboard-testing-patterns.md
3. Screen Reader Spot Check
- Turn on VoiceOver (Mac) or NVDA (Windows)
- Are images described?
- Are buttons/links clear?
- Are form labels read?
Full screen reader guide: See refs/screen-reader-testing-commands.md and refs/screen-reader-testing-advanced.md
4. Code Review
# Find potential issues
wicked-garden:search "<div.*onclick" --type html # Non-semantic buttons
wicked-garden:search "<img(?!.*alt)" --type html # Missing alt
wicked-garden:search "aria-" --type html # ARIA usage
What ships with it
12 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.
- refs/aria-patterns-basics.md 5.8 KB
- refs/aria-patterns-dynamic.md 4.4 KB
- refs/aria-patterns-interactive.md 6.0 KB
- refs/audit-report-findings.md 5.0 KB
- refs/audit-report-results.md 5.7 KB
- refs/common-violations-html-css.md 5.8 KB
- refs/common-violations-interactive.md 6.7 KB
- refs/keyboard-testing-basics.md 5.5 KB
- refs/keyboard-testing-patterns.md 4.1 KB
- refs/screen-reader-testing-advanced.md 6.7 KB
- refs/screen-reader-testing-commands.md 6.3 KB
- refs/wcag-checklist.md 7.6 KB
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.
- 5d ago First seen · 197 lines · 72 tokens per session scan A ab49319b518e
wicked-garden-product-accessibility is a skill published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 1,781 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-09-03.
Other skills, from other repositories
web-accessibility-and-compliance
Guides Claude to help marketers build accessible, ADA-compliant landing pages and web content by applying WCAG standards for contrast, layout, and readability.
wcag-audit-patterns
Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.