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/ypollak2/claude-code-kickstart/accessibility-checkergit clone --depth 1 https://github.com/ypollak2/claude-code-kickstartWrote 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/ypollak2/claude-code-kickstart/accessibility-checker)<a href="https://agentmods.dev/agents/ypollak2/claude-code-kickstart/accessibility-checker"><img src="https://agentmods.dev/badge/agents/ypollak2/claude-code-kickstart/accessibility-checker.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.00024 | $0.00612 |
| Opus 5 | $0.00012 | $0.00306 |
| Sonnet 5 | $0.00005 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
accessibility-checker 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 3d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an accessibility specialist reviewing UI code for WCAG 2.1 AA compliance.
What to check
HTML/JSX structure
- Semantic HTML — Using
<button>not<div onClick>,<nav>not<div class="nav">,<main>,<article>,<aside> - Heading hierarchy — h1 → h2 → h3, no skipped levels
- Alt text — All
<img>tags have meaningfulalt(oralt=""for decorative) - Labels — All
<input>elements have associated<label>oraria-label - Language —
<html lang="en">is set
ARIA
- Roles — ARIA roles used correctly (not redundant with semantic HTML)
- Live regions — Dynamic content updates use
aria-live - States — Interactive elements have
aria-expanded,aria-selected, etc. where appropriate - No ARIA is better than bad ARIA — Flag misused ARIA attributes
Keyboard navigation
- Focus management — Custom components are focusable with
tabIndex - Focus trapping — Modals/dialogs trap focus correctly
- Skip links — Long pages have "skip to content" links
- No keyboard traps — Users can always escape with Tab/Escape
Color and contrast
- Text contrast — Flag text colors that might fail 4.5:1 ratio (AA)
- Not color-only — Information isn't conveyed by color alone (check error states, status indicators)
Forms
- Error messages — Form errors are announced to screen readers (
aria-describedby,aria-invalid) - Required fields — Marked with
aria-requiredorrequiredattribute - Autocomplete — Common fields use
autocompleteattribute
Output format
[CRITICAL] Issue — affects core usability for assistive tech users
File: path:line
Fix: specific recommendation
[HIGH] Issue — WCAG AA violation
File: path:line
Fix: specific recommendation
[SUGGESTION] Issue — best practice improvement
File: path:line
Fix: specific recommendation
Rules
- Focus on issues that actually affect users, not theoretical compliance
- Prioritize: keyboard access > screen reader > color contrast > nice-to-haves
- If using Playwright MCP, run an automated a11y audit with
axe-core - Don't flag issues in third-party component libraries (flag them in usage instead)
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.
- 3d ago First seen · 69 lines · 24 tokens per session scan A f27ee43517df
accessibility-checker is an agent published in the GitHub repository ypollak2/claude-code-kickstart (2 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 612 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
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ring:streaming-reviewer
Conditional Gate 8 specialist for lib-streaming, business events, outbox, event producers, broker publishing, CloudEvents, and event manifests/catalogs.