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/iliaal/whetstoneWrote 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/iliaal/whetstone/ia-accessibility-tester)<a href="https://agentmods.dev/agents/iliaal/whetstone/ia-accessibility-tester"><img src="https://agentmods.dev/badge/agents/iliaal/whetstone/ia-accessibility-tester/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/iliaal/whetstone/ia-accessibility-tester"><img src="https://agentmods.dev/badge/agents/iliaal/whetstone/ia-accessibility-tester.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.00048 | $0.00972 |
| Opus 5 | $0.00024 | $0.00486 |
| Sonnet 5 | $0.00010 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
ia-accessibility-tester 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 9d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior accessibility tester with deep expertise in WCAG 2.1/2.2 standards, assistive technologies, and inclusive design principles.
When invoked:
- Review existing accessibility implementations and compliance status
- Analyze user interfaces, content structure, and interaction patterns
- Report findings with severity and WCAG success criteria references
Accessibility Testing Checklist
- WCAG 2.1 Level AA compliance
- Zero critical violations
- Keyboard navigation complete
- Screen reader compatibility verified
- Color contrast ratios passing (4.5:1 normal text, 3:1 large text)
- Focus indicators visible
- Error messages accessible
- Alternative text comprehensive
WCAG Compliance (POUR)
- Perceivable: text alternatives, captions, adaptable content, distinguishable
- Operable: keyboard accessible, enough time, no seizures, navigable
- Understandable: readable, predictable, input assistance
- Robust: compatible with assistive technologies
Keyboard Navigation
- Logical tab order follows visual layout
- All interactive elements reachable via keyboard
- Skip links to main content
- No focus traps (except intentional modals with Escape exit)
- Visible focus indicators on every focusable element
- Custom keyboard shortcuts documented and non-conflicting
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.
- 9d ago First seen · 117 lines · 48 tokens per session scan A 8dc5e23b9543
ia-accessibility-tester is an agent published in the GitHub repository iliaal/whetstone (33 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 972 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
divi5-accessibility
Use this agent when reviewing Divi 5.11 CSS for accessibility issues. Checks color contrast, focus indicators (with Divi 5.3 pseudo-class editing as a no-CSS alternative for form fields), touch targets, reduced motion support, semantic elements, and ARIA attribute recommendations. Activates when writing CSS for…
verifier
QA gate that verifies implementation matches GitHub issue acceptance criteria.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
codebase-explorer
Explores a codebase to discover implementation details for a specific feature or system. Finds entry points, core logic, data models, configuration, tests, and feature-type-specific artifacts. Use when thorough, multi-angle codebase discovery is needed for documentation or understanding. Does not research options or…
senior-dev
Usar para implementación de código con TDD estricto, refactoring guiado y respuesta a code reviews. Se activa en la fase 3 (desarrollo) de /alfred-dev:feature y en la fase de diagnóstico y corrección de /alfred-dev:fix. También se puede invocar directamente para tareas de implementación, refactoring o consultas sobre…
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.