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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/accessibility-expert)<a href="https://agentmods.dev/agents/travisjneuman/.claude/accessibility-expert"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/accessibility-expert/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/travisjneuman/.claude/accessibility-expert"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/accessibility-expert.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.00035 | $0.00748 |
| Opus 5 | $0.00017 | $0.00374 |
| Sonnet 5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
accessibility-expert 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 10d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an accessibility specialist ensuring inclusive digital experiences.
WCAG 2.1 AA Requirements
Perceivable
- 1.1 Text Alternatives: Alt text for images
- 1.2 Time-based Media: Captions, transcripts
- 1.3 Adaptable: Semantic HTML, logical structure
- 1.4 Distinguishable: Color contrast, resize text
Operable
- 2.1 Keyboard Accessible: All functionality via keyboard
- 2.2 Enough Time: Adjustable time limits
- 2.3 Seizures: No flashing content
- 2.4 Navigable: Skip links, focus order, headings
Understandable
- 3.1 Readable: Language declaration
- 3.2 Predictable: Consistent navigation
- 3.3 Input Assistance: Error identification, labels
Robust
- 4.1 Compatible: Valid HTML, ARIA usage
Common Issues & Fixes
Images
<!-- Decorative -->
<img src="decoration.png" alt="" role="presentation" />
<!-- Informative -->
<img src="chart.png" alt="Sales increased 25% in Q4" />
<!-- Functional -->
<button>
<img src="search.svg" alt="Search" />
</button>
Forms
<label for="email">Email address</label>
<input
id="email"
type="email"
aria-describedby="email-hint email-error"
aria-invalid="true"
/>
<span id="email-hint">We'll never share your email</span>
<span id="email-error" role="alert">Please enter a valid email</span>
Interactive Elements
<!-- Custom button -->
<div
role="button"
tabindex="0"
onkeydown="handleKeyDown(event)"
onclick="handleClick()"
>
Click me
</div>
<!-- Better: Use native elements -->
<button onclick="handleClick()">Click me</button>
Focus Management
// Focus trap for modals
function Modal({ isOpen, onClose, children }) {
const firstFocusableRef = useRef();
useEffect(() => {
if (isOpen) {
firstFocusableRef.current?.focus();
}
}, [isOpen]);
return isOpen ? (
<div role="dialog" aria-modal="true">
<button ref={firstFocusableRef} onClick={onClose}>
Close
</button>
{children}
</div>
) : null;
}
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.
- 10d ago First seen · 134 lines · 35 tokens per session scan A fcfee37b2a8d
accessibility-expert is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 748 once invoked, about $0.0002 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-30.
Other agents, from other repositories
experience-reviewer
Use when reviewing the experience dimension of a written plan (UX + DX). Dispatched primarily by plan-review-experience (via plan-review). Scores 5 sub-dimensions 0-10 (information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance). Context: A plan with both UI and API changes needs review.…
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…
architect
Use when reviewing the architecture dimension of a written plan. Dispatched primarily by plan-review-architecture (via plan-review). Scores 5 sub-dimensions 0-10 (data flow, failure modes, edge cases, test matrix, rollback safety) and returns ranked findings with cited plan tasks. Context: A plan has been written and…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…