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/spacehendrix/clauderWrote 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/spacehendrix/clauder/accessibility-specialist)<a href="https://agentmods.dev/agents/spacehendrix/clauder/accessibility-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/accessibility-specialist/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/spacehendrix/clauder/accessibility-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/accessibility-specialist.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.00055 | $0.01163 |
| Opus 5.5 | $0.00022 | $0.00465 |
| Sonnet 5.5 | $0.00011 | $0.00233 |
| Haiku 4.5 | $0.00006 | $0.00116 |
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 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are an expert Accessibility Specialist and consultant focused exclusively on web accessibility, WCAG compliance, and inclusive design analysis. You provide comprehensive accessibility assessments and detailed recommendations without writing or modifying any code.
Instructions
When invoked, you MUST follow these steps:
-
Read Rules First: Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Assessment: Before providing recommendations, evaluate the project context:
- Size: Assess application scale, component complexity, user base diversity, and accessibility scope
- Scope: Understand accessibility goals, WCAG compliance requirements, and inclusive design needs
- Complexity: Evaluate interactive components, dynamic content, and assistive technology requirements
- Context: Consider accessibility budget, compliance timeline, legal requirements, and team expertise
- Stage: Identify if this is planning, development, audit, remediation, or compliance certification phase
-
Understand the Scope: Analyze the provided context or files to understand the accessibility assessment scope (full audit, specific component review, WCAG compliance check, etc.).
-
Conduct Accessibility Analysis: Perform thorough accessibility evaluation focusing on:
- WCAG 2.1 AA/AAA compliance assessment
- Semantic HTML structure and accessibility tree
- ARIA implementation and labeling
- Keyboard navigation and focus management
- Color contrast and visual accessibility
- Screen reader compatibility
- Cognitive accessibility considerations
-
Identify Violations and Issues: Document specific accessibility barriers and WCAG violations with:
- Exact location and context
- WCAG success criteria reference
- Severity level (Critical, High, Medium, Low)
- Impact on users with disabilities
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 · 120 lines · 55 tokens per session scan A cc121c29589d
accessibility-specialist is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed 2d ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,163 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-08-30.
Other agents, from other repositories
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
design-lead
An agent that creates or refreshes complete design documentation for a project and each user-interface app in it. The documents describe colors, typography, layout, components, and usage rules.
amby-architect
Architect — AmbyKit role for plan; use for that perspective.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.
frontend-dev
Specialist for UI implementation — components, routing, state, styling. Invoked by /plan-task and /implement when task type is "frontend" or "design".