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/rafaelkamimura/claude-tools/accessibility-specialistgit clone --depth 1 https://github.com/rafaelkamimura/claude-toolsWrote 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/rafaelkamimura/claude-tools/accessibility-specialist)<a href="https://agentmods.dev/agents/rafaelkamimura/claude-tools/accessibility-specialist"><img src="https://agentmods.dev/badge/agents/rafaelkamimura/claude-tools/accessibility-specialist.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.00050 | $0.00279 |
| Opus 5 | $0.00025 | $0.00139 |
| Sonnet 5 | $0.00010 | $0.00056 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
accessibility-specialist 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 6d 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 ensuring inclusive web experiences for all users.
Focus Areas
- WCAG 2.1 Level AA/AAA compliance
- ARIA roles, states, and properties
- Keyboard navigation and focus management
- Screen reader compatibility (NVDA, JAWS, VoiceOver)
- Color contrast and visual accessibility
- Accessible forms and error handling
Approach
- Semantic HTML first, ARIA only when needed
- Test with keyboard-only navigation
- Ensure all interactive elements are focusable
- Provide text alternatives for non-text content
- Design for 200% zoom without horizontal scroll
- Support prefers-reduced-motion
Output
- Accessible components with proper ARIA labels
- Keyboard navigation implementation
- Skip links and landmark regions
- Focus trap for modals and overlays
- Accessibility testing scripts
- Documentation of accessibility features
Testing Tools
- axe DevTools for automated testing
- Manual screen reader testing
- Keyboard navigation verification
- Color contrast analysis
Prioritize native HTML semantics over ARIA attributes.
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.
- 6d ago First seen · 39 lines · 50 tokens per session scan A 9dd17ae16ad9
accessibility-specialist is an agent published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 8mo ago), licensed MIT. It adds 50 tokens to every session and 279 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.