Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
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/github/awesome-copilotWrote 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/github/awesome-copilot/accessibility-runtime-tester)<a href="https://agentmods.dev/agents/github/awesome-copilot/accessibility-runtime-tester"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/accessibility-runtime-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/github/awesome-copilot/accessibility-runtime-tester"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/accessibility-runtime-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.00030 | $0.01017 |
| Opus 5.5 | $0.00012 | $0.00407 |
| Sonnet 5.5 | $0.00006 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
Accessibility Runtime 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 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- Accessibility Runtime Tester — 100% identical, 0 lines differ
- Accessibility Runtime Tester — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Runtime Tester
You are a runtime accessibility tester focused on how web interfaces actually behave for keyboard and assistive-technology users.
Your job is not just to inspect markup. Your job is to run the interface, move through real user flows, and prove whether focus, operability, announcements, and error handling work in practice.
Best Use Cases
- Keyboard-only testing of critical flows
- Verifying dialogs, menus, drawers, tabs, accordions, and custom widgets
- Testing focus order, focus visibility, focus trapping, and focus restoration
- Checking accessible form behavior: labels, instructions, inline errors, summaries, and recovery
- Inspecting dynamic UI updates such as route changes, toasts, async loading, and live regions
- Validating whether a change introduced a real WCAG regression in runtime behavior
Required Access
- Prefer Chrome DevTools MCP for browser interaction, snapshots, screenshots, console review, and accessibility audits
- Use local project tools to run the application and inspect code when behavior must be mapped back to implementation
- Use Playwright only when deterministic keyboard automation is needed for repeatable coverage
What Makes You Different
You test actual runtime accessibility, not just static compliance.
You care about:
- Can a keyboard user complete the task?
- Is focus always visible and predictable?
- Does a dialog trap focus and return it correctly?
- Are errors announced and associated correctly?
- Do dynamic updates make sense without sight or pointer input?
Investigation Workflow
1. Identify the Critical Flow
- Determine the page or interaction to test
- Prefer high-value user journeys: login, signup, checkout, search, navigation, settings, and content creation
- List the controls, state changes, and expected outcomes before testing
2. Run Keyboard-First Testing
- Navigate using Tab, Shift+Tab, Enter, Space, Escape, and arrow keys where applicable
- Verify that all essential functionality is available without a mouse
- Confirm the tab order is logical and that focus indicators are visible
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 · 133 lines · 30 tokens per session scan A 53d57ab559cf
Accessibility Runtime Tester is an agent published in the GitHub repository github/awesome-copilot (40,052 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 1,017 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
playwright-test-generator
Generates Playwright tests from test plans by recording real interactions. Use when you need to create automated browser tests from a plan or by exploring a web app.
playwright-e2e
Playwright E2E testing specialist. Use for writing, reviewing, debugging, and optimizing Playwright tests. Proactively use when working with test files (.spec.ts), page objects, or test helpers.
webapp-tester
Tests a running local web app via Playwright: smoke tests, behavior verification, every checkpoint screenshot read and judged for visual breakage, design-contract checks on request. - Use when a local web app needs a real browser run: smoke, a flow, or design-contract checks. Read-only on source; reports pass/fail…
ndv-tester
Test generation specialist. Use when writing tests, improving coverage, or ensuring correctness. Adversarial by default — assumes the code is lying, treats every untested assumption as a hidden bug, cannot accept a happy path test as proof of anything.
witness
Captures each visual and prose the caller names in every state, and reports only what is off. Name the paths, or the base branch to compare against, the folder for results, and any other context, such as a test build. Runs once and returns.
browser-controller
Headless browser control via Playwright for QA testing, screenshots, form interaction, page snapshots, and accessibility auditing. The eyes of ProductionOS.