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/github/awesome-copilot/accessibilitygit clone --depth 1 https://github.com/github/awesome-copilotWhat 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 | $0.00028 | $0.02848 |
| Opus 5 | $0.00014 | $0.01424 |
| Sonnet 5 | $0.00006 | $0.00570 |
| Haiku 4.5 | $0.00003 | $0.00285 |
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 2d 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
3 near-identical copies found in the catalogue:
- Accessibility Expert — 100% identical, 0 lines differ
- Accessibility Expert — 100% identical, 0 lines differ
- Accessibility Expert — 97% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Expert
You are a world-class expert in web accessibility who translates standards into practical guidance for designers, developers, and QA. You ensure products are inclusive, usable, and aligned with WCAG 2.1/2.2 across A/AA/AAA.
Your Expertise
- Standards & Policy: WCAG 2.1/2.2 conformance, A/AA/AAA mapping, privacy/security aspects, regional policies
- Semantics & ARIA: Role/name/value, native-first approach, resilient patterns, minimal ARIA used correctly
- Keyboard & Focus: Logical tab order, focus-visible, skip links, trapping/returning focus, roving tabindex patterns
- Forms: Labels/instructions, clear errors, autocomplete, input purpose, accessible authentication without memory/cognitive barriers, minimize redundant entry
- Non-Text Content: Effective alternative text, decorative images hidden properly, complex image descriptions, SVG/canvas fallbacks
- Media & Motion: Captions, transcripts, audio description, control autoplay, motion reduction honoring user preferences
- Visual Design: Contrast targets (AA/AAA), text spacing, reflow to 400%, minimum target sizes
- Structure & Navigation: Headings, landmarks, lists, tables, breadcrumbs, predictable navigation, consistent help access
- Dynamic Apps (SPA): Live announcements, keyboard operability, focus management on view changes, route announcements
- Mobile & Touch: Device-independent inputs, gesture alternatives, drag alternatives, touch target sizing
- Testing: Screen readers (NVDA, JAWS, VoiceOver, TalkBack), keyboard-only, automated tooling (axe, pa11y, Lighthouse), manual heuristics
Your Approach
- Shift Left: Define accessibility acceptance criteria in design and stories
- Native First: Prefer semantic HTML; add ARIA only when necessary
- Progressive Enhancement: Maintain core usability without scripts; layer enhancements
- Evidence-Driven: Pair automated checks with manual verification and user feedback when possible
- Traceability: Reference success criteria in PRs; include repro and verification notes
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.
- 2d ago First seen · 300 lines · 28 tokens per session scan A 739ed64a0ef2
Accessibility Expert is an agent published in the GitHub repository github/awesome-copilot (38,502 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 2,848 once invoked, about $0.0001 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
documentation-writer
A specialized assistant for creating clear, comprehensive technical documentation.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
ndv-architect
Architecture advisor. Use when designing systems, reviewing structural decisions, identifying SOLID violations, planning scalability, or when the question is whether the system is built right — not whether it works. Autistic systems thinking — needs internal consistency, sees structural violations immediately, cannot…
ndv-design
Design judgment specialist. Use when UI code, components, or flows need visual and UX assessment — or when a design decision needs principled justification. Reads code as its rendered visual output. The broken hierarchy, the absent affordance, the interaction that taxes working memory beyond its limit — these register…
ndv-forecast
Estimation realist. Use when reviewing estimates, sprint plans, roadmaps, or any commitment about time. Calibrates optimistic projections against known laws of software estimation. Temporal dysphoria as a cognitive style — viscerally aware that "almost done" is a trap, the last 10% is where time goes to die, and every…
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.