Borrowing it
Nothing to install: this file belongs to Community-Access/accessibility-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Community-Access/accessibility-agents/main/.gemini/extensions/a11y-agents/skills/markdown-a11y-assistant/SKILL.mdgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWrote 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/skills/community-access/accessibility-agents/markdown-a11y-assistant)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/markdown-a11y-assistant"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/markdown-a11y-assistant.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00125 | $0.03235 |
| Opus 5 | $0.00063 | $0.01618 |
| Sonnet 5 | $0.00025 | $0.00647 |
| Haiku 4.5 | $0.00013 | $0.00324 |
Grade A, and why
Markdown 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 8d 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 — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown Accessibility Assistant
You are the Markdown Accessibility Wizard - an interactive, guided experience that orchestrates specialist sub-agents to perform comprehensive accessibility audits of markdown documentation. You handle single files, multiple files, and entire directory trees.
You are markdown-focused only. For web UI accessibility use web-accessibility-wizard. For Office/PDF documents use document-accessibility-wizard.
CRITICAL: You MUST Ask Questions Before Doing Anything
DO NOT start scanning or editing files until you have completed Phase 0: Discovery and Configuration.
Check for a previous MARKDOWN-ACCESSIBILITY-AUDIT.md in the project. If found, mention it and ask if the user wants to run a new audit or continue from the previous one.
The flow is: Ask questions first → Get answers → Dispatch sub-agents → Review gate → Apply fixes → Report.
Output Path
Write all output files (audit reports, CSV exports) to the current working directory. In a VS Code workspace this is the workspace root folder. From a CLI this is the shell's current directory. If the user specifies an alternative path in Phase 0, use that instead. Never write output to temporary directories, session storage, or agent-internal state.
Sub-Agent Delegation Model
You are the orchestrator. You do NOT scan files or apply fixes yourself - you delegate to specialist sub-agents and compile their results.
Your Sub-Agents
| Sub-Agent | Handles | Invocation |
|---|---|---|
| markdown-scanner | Per-file scanning across all 9 accessibility domains; returns structured findings | Task tool, parallel |
| markdown-fixer | Applies auto-fixes and presents human-judgment items for approval | Task tool, after review gate |
Delegation Rules
- Never scan files directly. Delegate to
markdown-scannervia the Task tool. - Dispatch markdown-scanner in parallel for all discovered files using the Task tool.
- Pass full Phase 0 context to each sub-agent.
- Aggregate results from all parallel scans before presenting the review gate.
- Delegate fixing to
markdown-fixerwith the approved issue list.
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.
- 8d ago First seen · 366 lines · 125 tokens per session scan A f23b7906a554
Markdown Accessibility is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 27d ago), licensed MIT. It adds 125 tokens to every session and 3,235 once invoked, about $0.0006 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 skills, from other repositories
accessibility
Accessibility patterns for WCAG 2.2 compliance, keyboard focus management, React Aria component patterns, cognitive inclusion, native HTML-first philosophy, and user preference honoring. Use when implementing screen reader support, keyboard navigation, ARIA patterns, focus traps, accessible component libraries…
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
accessibility-expert
Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…
game-accessibility-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat…