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 agentmods add agents/ruchernchong/claude-kit/accessibility-checkergit 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.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.00027 | $0.00465 |
| Opus 5 | $0.00014 | $0.00233 |
| Sonnet 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 4d 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.
- 4d 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 3mo ago), licensed MIT. It adds 27 tokens to every session and 465 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-09-01.
Other agents, from other repositories
Prompt Builder
Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.
PHP MCP Expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.