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 qte77/claude-code-plugins --skill auditing-website-accessibilitygit clone --depth 1 https://github.com/qte77/claude-code-pluginsWrote 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/qte77/claude-code-plugins/auditing-website-accessibility)<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/auditing-website-accessibility"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/auditing-website-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/qte77/claude-code-plugins/auditing-website-accessibility"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/auditing-website-accessibility.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.00043 | $0.00741 |
| Opus 5.5 | $0.00017 | $0.00296 |
| Sonnet 5.5 | $0.00009 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
auditing-website-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 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Website Accessibility Audit
Target: $ARGUMENTS
Conducts focused accessibility audits against WCAG 2.2 AA and generates implementable code fixes. No over-analysis.
WCAG Quick Reference
MUST READ references/wcag-quick-reference.md before auditing. Use it as
the checklist for all findings.
Audit Areas
Keyboard Navigation
- Tab order and focus management
- Skip links and keyboard shortcuts
- Focus indicators and styling
Screen Reader Compatibility
- ARIA landmarks and roles
- Semantic HTML structure
- Alternative text and descriptions
- Live region announcements
Visual Accessibility
- Color contrast ratios (4.5:1 minimum)
- Responsive zoom (200% minimum)
- Motion and animation controls
Forms and Data Tables
- Label associations and error handling
- Fieldset/legend usage and required field indicators
- Table header associations and caption elements
Workflow
- Identify scope from $ARGUMENTS (URL, file, or directory)
- Run automated checks (axe-core, HTML validation, contrast ratios)
- Manual review (keyboard-only navigation, screen reader, 200% zoom)
- Classify findings by WCAG level and impact
- Generate code fixes for each finding
Output Format
Findings
CRITICAL (WCAG Level A)
- [Issue] - Impact: [High/Medium/Low] - Element: [selector]
Fix: [Code snippet]
WCAG: [Success Criterion]
COMPLIANCE (WCAG Level AA)
- [Issue] - Impact: [High/Medium/Low] - Element: [selector]
Fix: [Code snippet]
WCAG: [Success Criterion]
Implementation Checklist
- [ ] [Fix description] - Impact: [High/Medium/Low]
Group fixes by: Keyboard Navigation, Screen Readers, Visual, Forms/Tables.
Rules
- Prioritize Level A violations before Level AA
- Every finding must include a specific, implementable code fix
- Test keyboard navigation and screen reader paths manually
- Keep output concise: findings + fixes + checklist only
Further Reading
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 First seen · 98 lines · 43 tokens per session scan A ee1ab06c7ac4
auditing-website-accessibility is a skill published in the GitHub repository qte77/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 741 once invoked, about $0.0002 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
customer-journey-map
Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities. Use when mapping the customer experience, identifying friction points, improving onboarding, or visualizing the user journey.
steve-jobs-design-review
Review designs, products, and features with Steve Jobs' standards: ruthless simplicity, focus, and end-to-end excellence. Use when the user mentions "Steve Jobs review", "design review", "product review", "what would Steve do", "insanely great", "this feels too complicated", "too many features", "product taste"…
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
web-typography
Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", "typographic scale", or "the text is hard to read". Also trigger when choosing between system…
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
design-sprint
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product…