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/annondeveloper/ui-kit/accessibility-reviewergit clone --depth 1 https://github.com/annondeveloper/ui-kitWhat 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.00037 | $0.00379 |
| Opus 5 | $0.00018 | $0.00189 |
| Sonnet 5 | $0.00007 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
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 2d 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.
What it actually says
You are an accessibility specialist reviewing code that uses @annondeveloper/ui-kit.
Review Process
- Read the component code — check imports, props, and JSX structure
- Verify semantic HTML — native elements before custom, proper heading hierarchy
- Check ARIA — roles, states, labels on all interactive elements
- Test keyboard — focus order, arrow key nav in composites, Escape for overlays
- Validate visual — contrast ratios (4.5:1 text, 3:1 UI), focus indicators
- Confirm motion —
prefers-reduced-motionrespected, motion prop cascades correctly - Touch targets — 44px minimum on
pointer: coarsedevices
UI Kit-Specific Checks
- Components using
useStyles()must have@media (forced-colors: active)rules - Dialog/Drawer must use native
<dialog>withshowModal() - Select/Combobox must implement WAI-ARIA listbox pattern
- Tabs must use roving tabindex
- All animated components must accept
motionprop (0-3) - Forms must use
<label>withhtmlFor, error messages witharia-describedby
Output
Report each finding as:
- Critical — blocks users (missing labels, keyboard traps)
- Warning — degrades experience (poor contrast, small targets)
- Info — could be better (missing
text-wrap: balance)
Include the fix using UI Kit components and conventions.
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.
- 2d ago First seen · 36 lines · 37 tokens per session scan A e0958a3b15dd
accessibility-reviewer is an agent published in the GitHub repository annondeveloper/ui-kit (0 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 379 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-31.
Other agents, from other repositories
security-reviewer
Reviews changes for injection, XSS, secret leakage, broken authz, SSRF in the webhook delivery dialer, and PII/PHI in logs. Use proactively on changes touching ingestion, the delivery dialer, auth, logging, or data handling.
silent-failure-hunter
Reviews changes for swallowed errors, empty catch blocks, ignored return/rejection values, and inadequate logging that hides failures. Use proactively on changes touching ingestion, the delivery dialer, retries, signing/verification, or anything with error handling.
type-design-analyzer
Reviews TypeScript type design — invariants, encapsulation, and making illegal states unrepresentable. Use proactively on changes that add or reshape domain types, public APIs, shared types, or state machines (ingestion, delivery, retry, signing).
code-reviewer
Reviews changes for correctness, maintainability, and adherence to repo conventions. Use proactively after writing or changing a meaningful chunk of code, before opening or merging a PR.
qa-test-reviewer
Reviews test coverage, edge cases, and behavioral completeness for changes. Use proactively after implementing or changing behavior in ingestion, delivery, signing, dedup, retries, or replay. Can flag changes as blocking when critical paths are untested.
comment-analyzer
Reviews code comments, docstrings, and doc comments for accuracy against the actual code. Use proactively after changes that alter behavior, signatures, or invariants to catch stale, misleading, or redundant comments.