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.
git clone --depth 1 https://github.com/CrashBytes/claude-role-skillsWrote 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/commands/crashbytes/claude-role-skills/accessibility-audit)<a href="https://agentmods.dev/commands/crashbytes/claude-role-skills/accessibility-audit"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/accessibility-audit.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.00016 | $0.00568 |
| Opus 5 | $0.00008 | $0.00284 |
| Sonnet 5 | $0.00003 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
accessibility-audit 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 7d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Audit
Run a WCAG 2.1 AA compliance audit on a component, page, or set of files.
Arguments
Target to audit: $ARGUMENTS
Workflow
-
Identify audit scope
- If a file path is provided, read it and any related component files
- If a component name is provided, search the codebase for it
- If no argument, scan for common UI entry points (pages, layouts, app root)
-
Perceivable (WCAG 1.x)
- Color contrast: Check for hardcoded colors, verify 4.5:1 for normal text, 3:1 for large text
- Images: Check all
<img>tags have meaningfulaltattributes (decorative images should usealt="") - Text alternatives: Check for
aria-labeloraria-labelledbyon icon-only buttons - Responsive: Check for viewport meta, no horizontal scroll at 320px
-
Operable (WCAG 2.x)
- Keyboard: Check all interactive elements are natively focusable (
<button>,<a>,<input>) or havetabindex - Focus indicators: Check for
outline: nonewithout replacement focus styles - Click targets: Check for minimum 44x44px touch targets
- Skip navigation: Check for skip-to-content link
- Keyboard: Check all interactive elements are natively focusable (
-
Understandable (WCAG 3.x)
- Form labels: Check all inputs have associated
<label>elements (not just placeholder) - Error messages: Check form validation provides specific, helpful messages
- Language: Check
<html lang="...">is set - Consistent navigation: Check for predictable layout patterns
- Form labels: Check all inputs have associated
-
Robust (WCAG 4.x)
- Semantic HTML: Flag
<div>or<span>used for interactive elements instead of<button>,<a>,<nav> - ARIA usage: Check ARIA attributes are used correctly (prefer native HTML over ARIA)
- Duplicate IDs: Scan for duplicate
idattributes - Valid nesting: Check heading hierarchy (no skipped levels)
- Semantic HTML: Flag
-
Output
- Issues grouped by WCAG principle
- Severity rating: Critical / Major / Minor
- Specific file, line number, and code snippet for each issue
- Fix recommendation for each issue
- Compliance summary: pass / partial / fail
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.
- 7d ago First seen · 52 lines · 16 tokens per session scan A 7d9fc4a0905f
accessibility-audit is a command published in the GitHub repository CrashBytes/claude-role-skills (6 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 568 once invoked, about $0.0001 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 commands, from other repositories
customize
Modify site appearance through frontmatter.
color-palette
Generate an accessible colour palette from a hex value.
ux-extract
Exhaustively extract UX patterns from a reference web app into a reusable pattern library.
summary
Generate a consolidated project brief from design artifacts. For the full spec package with YAML specs and validation, use /compile instead.
design-review
Structured design review of the current build or a URL — hierarchy, consistency, taste, polish.
close-sprint
Close the sprint — record Increment + velocity, return unfinished stories/bugs to the backlog.