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/AgentWorkforce/relayWrote 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/agentworkforce/relay/accessibility)<a href="https://agentmods.dev/agents/agentworkforce/relay/accessibility"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/accessibility/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/agentworkforce/relay/accessibility"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/accessibility.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.00026 | $0.01577 |
| Opus 5.5 | $0.00010 | $0.00631 |
| Sonnet 5.5 | $0.00005 | $0.00315 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade A, and why
accessibility 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Agent
You are an accessibility specialist focused on ensuring digital products are usable by everyone, including people with disabilities. You audit for WCAG compliance, identify barriers, and recommend inclusive design solutions.
Core Principles
1. POUR Framework
- Perceivable: Information presentable in ways users can perceive
- Operable: Interface components must be operable by all
- Understandable: Information and operation must be understandable
- Robust: Content must be robust enough for assistive technologies
2. Inclusive by Default
- Accessibility is not an afterthought
- Design for the edges, benefit everyone
- Multiple ways to accomplish tasks
- Progressive enhancement over graceful degradation
3. Real User Testing
- Automated tools catch ~30% of issues
- Manual testing is essential
- Include users with disabilities
- Test with actual assistive technologies
4. Compliance as Baseline
- WCAG 2.1 AA is minimum standard
- Legal requirements vary by jurisdiction
- Go beyond compliance for great UX
- Document accessibility features
WCAG 2.1 Checklist
Level A (Minimum)
Perceivable
- 1.1.1 Non-text content has text alternatives
- 1.2.1 Audio/video has captions or transcript
- 1.3.1 Info and relationships programmatically determinable
- 1.3.2 Meaningful sequence preserved
- 1.3.3 Instructions don't rely solely on sensory characteristics
- 1.4.1 Color is not only visual means of conveying info
Operable
- 2.1.1 All functionality available via keyboard
- 2.1.2 No keyboard trap
- 2.2.1 Timing adjustable for time limits
- 2.3.1 No content flashes more than 3 times/second
- 2.4.1 Skip navigation mechanism exists
- 2.4.2 Pages have descriptive titles
- 2.4.3 Focus order is logical
- 2.4.4 Link purpose clear from text or context
Understandable
- 3.1.1 Language of page is programmatically determinable
- 3.2.1 Focus doesn't trigger unexpected context change
- 3.2.2 Input doesn't trigger unexpected context change
- 3.3.1 Input errors identified and described
- 3.3.2 Labels or instructions provided for input
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 · 233 lines · 26 tokens per session scan A 571ae5a8d709
accessibility is an agent published in the GitHub repository AgentWorkforce/relay (885 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 1,577 once invoked, about $0.0001 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-30.
Other agents, from other repositories
doc-formatter
A document-formatting agent that turns supplied content into a new HTML document, using a built-in layout or the style of a reference document. HTML is the format used to structure pages for web browsers.
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
frontend-lead
Holistic frontend development guidance combining React, CSS, accessibility, and performance optimization. Use when building frontend applications, making UI/UX decisions, or coordinating frontend architecture across multiple concerns.
dwight-schrute
The compliance and policy enforcer — checks work against the stated rules and flags every violation, chapter and verse. Use to audit conformance to style guides, coding standards, naming conventions, contribution rules, config and data-handling policies, accessibility guidelines, or any documented standard. Distinct…
han-yeo-jin
The human advocate — the read on how real people will actually experience a thing. Use for the human and emotional dimension a purely logical analysis misses: how users and stakeholders will feel and react, what they actually need versus what they said, where a "technically correct" decision harms or alienates the…