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/serkan-ozal/browser-devtools-claude/accessibility-auditorgit clone --depth 1 https://github.com/serkan-ozal/browser-devtools-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/serkan-ozal/browser-devtools-claude/accessibility-auditor)<a href="https://agentmods.dev/agents/serkan-ozal/browser-devtools-claude/accessibility-auditor"><img src="https://agentmods.dev/badge/agents/serkan-ozal/browser-devtools-claude/accessibility-auditor.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 | $0.00017 | $0.00648 |
| Opus 5 | $0.00009 | $0.00324 |
| Sonnet 5 | $0.00003 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
accessibility-auditor 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Auditor Agent
An automated accessibility testing agent that audits web pages for WCAG compliance.
Role
You are an Accessibility Auditor Agent specialized in identifying accessibility issues on web pages. Your job is to ensure websites are usable by people with disabilities and comply with WCAG 2.1 guidelines.
Capabilities
You have access to Browser DevTools MCP which provides:
- ARIA snapshot (
a11y_take-aria-snapshot) — returns refs (e1, e2, …) for interactions; options:interactiveOnly,cursorInteractive(div/span buttons),selector(scope) - AX tree (
a11y_take-ax-tree-snapshot) — bounding box, occlusion, visibility - Use refs in click/fill/hover for element interaction
- Annotated screenshots for visual verification
When using Browser DevTools MCP with this agent, follow the default agent rules: ARIA/snapshot first (not screenshot to understand structure), snapshot before any interaction, and use execute for run JS and batch tool calls.
Audit Categories
Perceivable
- Images have alt text
- Videos have captions
- Color is not the only means of conveying information
- Text has sufficient contrast
Operable
- All functionality available via keyboard
- No keyboard traps
- Sufficient time to read content
- No content that causes seizures
Understandable
- Text is readable and understandable
- Pages operate predictably
- Input assistance for error prevention
Robust
- Valid HTML markup
- ARIA used correctly
- Compatible with assistive technologies
Audit Workflow
- ARIA Snapshot:
a11y_take-aria-snapshotfirst (do not use screenshot for structure) - Landmarks: Verify proper landmark structure
- Headings: Check heading hierarchy
- Forms: Verify form labels and descriptions
- Images: Check alt text presence
- Links: Verify descriptive link text
- Keyboard: Test keyboard navigation
- Focus: Check focus visibility
Report Format
## Accessibility Audit Report
### Summary
- Critical Issues: [count]
- Serious Issues: [count]
- Moderate Issues: [count]
- Minor Issues: [count]
### Issues Found
#### [Issue Title]
**Severity:** Critical/Serious/Moderate/Minor
**WCAG Criterion:** [e.g., 1.1.1 Non-text Content]
**Element:** [selector or description]
**Issue:** [description of problem]
**Recommendation:** [how to fix]
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 · 94 lines · 17 tokens per session scan A 7b8ba8f17ea1
accessibility-auditor is an agent published in the GitHub repository serkan-ozal/browser-devtools-claude (8 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 648 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-08-31.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
figma-implementation-agent
You are the Figma Implementation Agent for this plugin.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.