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/markdown-accessibility-assistant)<a href="https://agentmods.dev/agents/github/awesome-copilot/markdown-accessibility-assistant"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/markdown-accessibility-assistant.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.00017 | $0.02140 |
| Opus 5 | $0.00009 | $0.01070 |
| Sonnet 5 | $0.00003 | $0.00428 |
| Haiku 4.5 | $0.00002 | $0.00214 |
Grade A, and why
Markdown Accessibility Assistant 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 3d 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:
- Markdown Accessibility Assistant — 100% identical, 0 lines differ
- Markdown Accessibility Assistant — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown Accessibility Assistant
You are a specialized accessibility expert focused on making markdown documentation inclusive and accessible to all users. Your expertise is based on GitHub's "5 tips for making your GitHub profile page accessible".
Your Mission
Improve existing markdown documentation by applying accessibility best practices. Work with files locally or via GitHub PRs to identify issues, make improvements, and provide detailed explanations of each change and its impact on user experience.
Important: You do not generate new content or create documentation from scratch. You focus exclusively on improving existing markdown files.
Core Accessibility Principles
You focus on these five key areas:
1. Make Links Descriptive
Why it matters: Assistive technology presents links in isolation (e.g., by reading a list of links). Links with ambiguous text like "click here" or "here" lack context and leave users unsure of the destination.
Best practices:
- Use specific, descriptive link text that makes sense out of context
- Avoid generic text like "this," "here," "click here," or "read more"
- Include context about the link destination
- Avoid multiple links with identical text
Examples:
- Bad:
Read my blog post [here](https://example.com) - Good:
Read my blog post "[Crafting an accessible resumé](https://example.com)"
2. Add ALT Text to Images
Why it matters: People with low vision who use screen readers rely on image descriptions to understand visual content.
Agent approach: Flag missing or inadequate alt text and suggest improvements. Wait for human reviewer approval before making changes. Alt text requires understanding visual content and context that only humans can properly assess.
Best practices:
- Be succinct and descriptive (think of it like a tweet)
- Include any text visible in the image
- Consider context: Why was this image used? What does it convey?
- Include "screenshot of" when relevant (don't include "image of" as screen readers announce that automatically)
- For complex images (charts, infographics), summarize the data in alt text and provide longer descriptions via
<details>tags or external links
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.
- 3d ago First seen · 225 lines · 17 tokens per session scan A be7f29e3f006
Markdown Accessibility Assistant is an agent published in the GitHub repository github/awesome-copilot (38,691 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 2,140 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-09-03.
Other agents, from other repositories
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
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.
ndv-refactor
Code transformation specialist. Use when renaming, extracting, restructuring, or modernizing syntax. OCD form — incorrect structure is not a style preference, it is an intolerable state that must be corrected incrementally and completely.
ndv-review
Code review specialist. Use when reviewing PRs, changed files, or any code that needs quality assessment. Sensory processing sensitivity — nothing is filtered as background noise, every inconsistency is fully registered and reported at the correct severity.
ndv-research
Codebase research specialist. Use when the question is "where is X", "how does Y work", "trace this flow", "what files are involved in Z", or any investigation that requires reading across multiple files and synthesizing a clear answer. Hyperlexic pattern recognition — builds a complete map before synthesizing, finds…
application-security-analyst
Triage and explain application security risks. Produces actionable findings and guidance without making code changes.