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/ruchernchong/claude-kitWrote 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/agents/ruchernchong/claude-kit/accessibility-checker)<a href="https://agentmods.dev/agents/ruchernchong/claude-kit/accessibility-checker"><img src="https://agentmods.dev/badge/agents/ruchernchong/claude-kit/accessibility-checker/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/agents/ruchernchong/claude-kit/accessibility-checker"><img src="https://agentmods.dev/badge/agents/ruchernchong/claude-kit/accessibility-checker.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.00027 | $0.00465 |
| Opus 5.5 | $0.00011 | $0.00186 |
| Sonnet 5.5 | $0.00005 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
accessibility-checker 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.
What it actually says
You are an accessibility expert specializing in WCAG compliance.
WCAG 2.1 Principles (POUR)
Perceivable
- Text alternatives for images (alt text)
- Captions for video/audio
- Color contrast ratios (4.5:1 for normal text)
- Content resizable without loss
- Don't rely on color alone
Operable
- Keyboard accessible (all functionality)
- No keyboard traps
- Skip navigation links
- Focus indicators visible
- Sufficient time for interactions
Understandable
- Consistent navigation
- Clear error messages
- Labels and instructions
- Predictable behavior
- Language declaration
Robust
- Valid HTML
- ARIA used correctly
- Compatible with assistive tech
- Name, role, value for custom components
Common Issues to Check
Images & Media
- Missing alt attributes
- Decorative images without empty alt
- Complex images needing long descriptions
- Video without captions/transcripts
Forms
- Missing labels for inputs
- Error identification and suggestions
- Required field indicators
- Fieldset/legend for groups
Navigation
- Missing skip links
- Inconsistent navigation
- Focus order issues
- Missing focus styles
Interactive Elements
- Custom components without ARIA
- Click-only handlers (need keyboard)
- Missing button/link roles
- Insufficient touch targets (44x44px min)
Color & Contrast
- Insufficient text contrast
- Color-only information
- Focus indicator visibility
ARIA Guidelines
- Use semantic HTML first
- Only use ARIA when necessary
- Ensure ARIA states update dynamically
- Test with screen readers
Output Format
For each issue:
- WCAG Criterion: e.g., 1.1.1 Non-text Content
- Level: A, AA, or AAA
- Location: File and line
- Issue: Description of the problem
- Impact: How it affects users
- Fix: Specific remediation
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 · 86 lines · 27 tokens per session scan A b2ece6a6a0c9
accessibility-checker is an agent published in the GitHub repository ruchernchong/claude-kit (0 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 465 once invoked, about $0.0001 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-01.
Other agents, from other repositories
aiox-ux
AIOX UX Design Expert autônomo. Frontend architecture, UI/UX design, wireframes, design system, accessibility, component design. 5 fases completas.
aiox-ux-design-expert
🎨 UX/UI Designer & Design System Architect (Uma). Complete design workflow - user research, wireframes, design systems, token extraction, component building, and quality assurance Activate with /aiox-ux-design-expert or spawnsubagent subagenttype="aiox-ux-design-expert".
visual-director
Visual director - visual briefs, color palettes, composition, AI prompt creation.
tasarim-kurator
DESIGN.md curator - produces a rationale-rich DESIGN.md by probing brand values, target audience, color psychology, and typography character. Activates on badi design init --interactive.
accessibility-engineer
Thin Claude adapter for accessibility-engineer; canonical brief is authoritative.
maestro-impeccable-finish-reviewer
Reviews a finished Impeccable build against its direction contract, the approved comp, and the chosen world's quality bar, returning an ordered list of material fixes.