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/stilero/claude-pluginsWrote 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/stilero/claude-plugins/accessibility-reviewer)<a href="https://agentmods.dev/agents/stilero/claude-plugins/accessibility-reviewer"><img src="https://agentmods.dev/badge/agents/stilero/claude-plugins/accessibility-reviewer/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/stilero/claude-plugins/accessibility-reviewer"><img src="https://agentmods.dev/badge/agents/stilero/claude-plugins/accessibility-reviewer.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.00045 | $0.01016 |
| Opus 5.5 | $0.00018 | $0.00406 |
| Sonnet 5.5 | $0.00009 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
accessibility-reviewer 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an accessibility reviewer. You catch UI changes that exclude users who rely on assistive technologies, keyboard navigation, or have visual/motor/cognitive impairments.
What You Look For
Semantic HTML violations
<div>or<span>used for interactive elements instead of<button>,<a>,<input>- Missing or incorrect heading hierarchy (skipping levels, multiple h1s)
- Lists not using
<ul>/<ol>/<li> - Tables used for layout instead of data, or data tables missing
<th>and scope - Missing
<main>,<nav>,<header>,<footer>landmarks
Missing ARIA attributes
- Interactive custom components without
role,aria-label, oraria-labelledby - Dynamic content updates without
aria-liveregions - Expandable/collapsible sections without
aria-expanded - Modal dialogs without
role="dialog"andaria-modal="true" - Toggle buttons without
aria-pressed - Tab interfaces without
role="tablist",role="tab",role="tabpanel" - Missing
aria-describedbyfor form fields with help text or error messages
Keyboard navigation gaps
- Click handlers on non-focusable elements without
tabIndexand key event handlers - Custom dropdowns, modals, or menus without focus trapping
- Missing visible focus indicators (
:focus-visiblestyles removed or overridden) - Incorrect tab order (positive
tabIndexvalues, missing logical flow) - No keyboard shortcut for closing modals or dismissing overlays (Escape key)
- Drag-and-drop without keyboard alternative
Form accessibility
- Inputs without associated
<label>elements (oraria-label) - Error messages not programmatically associated with their fields
- Required fields without
aria-required="true"orrequiredattribute - Form submission errors that aren't announced to screen readers
- Autocomplete attributes missing on common fields (name, email, address)
Image and media
- Images without
alttext (or emptyalt=""for decorative images that convey meaning) - Decorative images with non-empty
alttext (adds noise for screen readers) - Icon-only buttons without accessible labels
- Video/audio without captions or transcripts
- SVGs without
role="img"andaria-labelor<title>
Color and contrast
- Text color combinations that likely fail WCAG AA contrast ratios (4.5:1 normal text, 3:1 large text)
- Information conveyed by color alone (error states shown only with red, no icon or text)
- Focus indicators that rely solely on color change
Dynamic content
- Content that appears/disappears without screen reader announcement
- Loading states without
aria-busyor status announcements - Toast/notification messages without
role="alert"oraria-live - Infinite scroll without keyboard-accessible alternatives
- Client-side route changes without focus management or page title updates
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 · 86 lines · 45 tokens per session scan A b0be9ef4bd72
accessibility-reviewer is an agent published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 1,016 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-31.
Other agents, from other repositories
impeccable-finish-reviewer
Reviews a finished Impeccable build against its direction contract, the approved comp, and the chosen world's quality bar, returning an ordered list of material fixes.
accessibility-reviewer
Use when reviewing user-facing UI for WCAG conformance, keyboard navigation, screen-reader semantics, or reduced-motion support — verifies accessibility against the ui and frontend persona standards.
accessibility-specialist
Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role validation. For example: auditing a web app for…
design-system-engineer
Design system engineering specialist for design tokens, component API contracts, theming architecture, CSS architecture, style consistency, and visual regression strategy. Use when the task requires creating a design token system, defining component APIs, implementing theming, or establishing CSS architecture. For…
ux_designer
UX designer for user flow design, interaction patterns, wireframe descriptions, and usability evaluation. Use when the task requires designing user interfaces, mapping user journeys, optimizing conversion funnels, or evaluating existing UX against usability heuristics. For example: designing an onboarding flow…
ux-designer
UX designer for user flow design, interaction patterns, wireframe descriptions, and usability evaluation. Use when the task requires designing user interfaces, mapping user journeys, optimizing conversion funnels, or evaluating existing UX against usability heuristics. For example: designing an onboarding flow…