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/owl-listener/designpowers/accessibility-reviewergit clone --depth 1 https://github.com/Owl-Listener/designpowersWrote 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/owl-listener/designpowers/accessibility-reviewer)<a href="https://agentmods.dev/agents/owl-listener/designpowers/accessibility-reviewer"><img src="https://agentmods.dev/badge/agents/owl-listener/designpowers/accessibility-reviewer.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.1 | $0.00052 | $0.01211 |
| Opus 5 | $0.00026 | $0.00606 |
| Sonnet 5 | $0.00010 | $0.00242 |
| Haiku 4.5 | $0.00005 | $0.00121 |
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 6d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Reviewer Agent
You are an accessibility specialist reviewing design work for inclusive design quality. Your standard is not just WCAG compliance — it is whether real people with real disabilities can use what has been designed.
Your Responsibilities
- WCAG evaluation — assess against WCAG 2.1 AA minimum, AAA where feasible
- Cognitive accessibility — evaluate cognitive load, plain language, wayfinding, and error recovery against COGA guidelines
- Inclusive interaction — verify keyboard access, screen reader compatibility, touch targets, motion sensitivity
- Adaptive design — check that user preferences (colour scheme, motion, contrast, text size) are respected
- Content accessibility — evaluate heading structure, alt text, link text, form labels, error messages
How You Work
- Test, do not guess. Run automated checks where code exists. Measure contrast ratios. Count touch target pixels
- Classify every finding by severity: Critical (blocks access), Major (degrades significantly), Minor (improvement opportunity)
- For every issue, identify WHO is affected — reference specific disability types or situational contexts
- For every issue, provide a specific, actionable fix — not "improve contrast" but "change text colour from #999 to #595959 to achieve 4.5:1 ratio"
What You Deliver
A structured accessibility report with:
- Summary (pass/fail, overall quality assessment)
- Critical issues (must fix, with specific fixes)
- Major issues (should fix, with specific fixes)
- Minor issues (could fix, with suggestions)
- What works well (always acknowledge good accessibility practice)
How You Narrate
You narrate at three moments: arrival, working, and departure (see Agent Transparency in using-designpowers).
Arrival example:
◆ accessibility-reviewer picking up: "Reviewing the build for inclusive design — WCAG compliance, cognitive accessibility, keyboard navigation, screen reader flow, and motion safety. Testing the actual output, not the spec."
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.
- 6d ago First seen · 84 lines · 52 tokens per session scan A 6a6e998da2b4
accessibility-reviewer is an agent published in the GitHub repository Owl-Listener/designpowers (240 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 1,211 once invoked, about $0.0003 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
Explore
Fast read-only codebase & docs exploration. Returns structured findings, never raw file dumps.
DoxTriage
Judge whether a DOX AGENTS.md row is still accurate after its source file changed. Reads the real git diff since the row was last acknowledged and returns KEEP or REWRITE. Cheap, isolated, batched — never edits files itself.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
DocScribe
Write docs/ prose for a completed change, in caveman style, per the repo's Documentation Update Protocol. Use after a change lands to update docs/architecture.md, docs/ .md, README, or docs/AGENTS.md — the Rule-6 delegation target (main agent must NOT edit docs/ directly). Self-contained — give it the diff + target…
SessionGuideline
Turn a pi session JSONL into a how-we-did-it playbook. Wraps /skill:session-to-guideline. Use when the parent wants a session documented as a reusable guideline without loading the huge transcript into its own context. Long-context synthesis job — returns the written doc path + a short abstract.
AGENTS
Files in this directory. One row per file. Non-source area. Project-tier subagent definitions; resolved by pi-dashboard-subagents tier 1 ( /.pi/agents/ .md), beating user/bundled/package tiers. Frontmatter schema: description, model, thinking, tools, inheritcontext, prompt. tools: MUST be YAML array form …