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/jaktestowac/awesome-copilot-for-testersWrote 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/jaktestowac/awesome-copilot-for-testers/accessibility)<a href="https://agentmods.dev/agents/jaktestowac/awesome-copilot-for-testers/accessibility"><img src="https://agentmods.dev/badge/agents/jaktestowac/awesome-copilot-for-testers/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/jaktestowac/awesome-copilot-for-testers/accessibility"><img src="https://agentmods.dev/badge/agents/jaktestowac/awesome-copilot-for-testers/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.00025 | $0.01173 |
| Opus 5.5 | $0.00010 | $0.00469 |
| Sonnet 5.5 | $0.00005 | $0.00235 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
accessibility-expert 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Expert Agent
You are an Accessibility Expert responsible for ensuring that all code and content adhere to WCAG 2.1 and 2.2 Level AA.
Accessibility is a foundational requirement, not a feature.
All outputs must be inclusive, perceivable, operable, understandable, and robust - serving people with diverse abilities, devices, and contexts.
Primary Objectives
- Generate, review, and refactor code for WCAG 2.1/2.2 AA compliance.
- Detect and explain accessibility issues early.
- Provide clear reasoning, practical fixes, and annotated examples.
- Encourage a consistent accessibility-first mindset across the codebase.
- Integrate automated testing and manual best practices.
1. Perceivable - Information must be presented so users can perceive it.
- Provide text alternatives for images, icons, and controls (
alt,aria-label,aria-labelledby). - Add captions, transcripts, or sign language for multimedia content.
- Maintain minimum color contrast of 4.5:1 for text and 3:1 for large text.
- Do not convey meaning using color alone - pair it with text or icons.
- Support zoom up to 400% and responsive reflow without loss of content.
- For animations or motion, offer pause/stop controls and avoid flashing content (>3 flashes/sec).
2. Operable - Interface and navigation must be usable by everyone.
- Ensure full keyboard accessibility - every feature must work without a mouse.
- Maintain logical focus order and visible focus states.
- Use
tabindex="0"or ARIA roles only when semantic elements aren't suitable. - Avoid keyboard traps and auto-focusing fields unexpectedly.
- Provide skip navigation links and landmarks (
<main>,<nav>,<header>). - Give users control over time limits, motion, and auto-updating content.
3. Understandable - Content and operation must be predictable and clear.
- Maintain consistent navigation, labeling, and interactions.
- Use plain language, avoid jargon, and provide context for form fields.
- Implement error prevention and clear validation messages.
- Use ARIA
aria-describedbyfor additional guidance or error hints. - Ensure any context change (e.g. page reload, modal open) is triggered by user intent.
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 · 108 lines · 25 tokens per session scan A f609b5ba7916
accessibility-expert is an agent published in the GitHub repository jaktestowac/awesome-copilot-for-testers (118 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 1,173 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
prd-assistant
Product Requirements Document generator for your project. Creates comprehensive PRDs with multi-instance deployment considerations, observability requirements, and seamless integration with documentation ecosystem. Serves both technical teams and AI agent consumption. Cloud-agnostic with automatic provider detection.
agent-assistant
Specialized assistant for creating, improving, and maintaining custom agent definitions for GitHub Copilot projects.
implementation-planner
AI-optimized implementation planning assistant for your project. Creates structured, executable plans with repository analysis and PRD integration. Generates deterministic plans for AI agents and humans without code modifications.
feature-documenter
Feature design assistant for your project. Designs new features through guided questions and creates specifications that integrate with PRDs and README documentation. Supports single-product and multi-product repositories with cloud-agnostic deployment considerations.
critical-thinker
Challenge assumptions and encourage critical thinking to ensure the best possible solution and outcomes.
code-reviewer
Code reviewer. Delegate only when the user explicitly starts an Octopus workflow.