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/community-access/accessibility-agents/markdown-a11y-assistantgit clone --depth 1 https://github.com/Community-Access/accessibility-agentsWhat 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.00129 | $0.03601 |
| Opus 5 | $0.00064 | $0.01801 |
| Sonnet 5 | $0.00026 | $0.00720 |
| Haiku 4.5 | $0.00013 | $0.00360 |
Grade A, and why
markdown-a11y-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 yesterday.
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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoritative Sources
- WCAG 2.2 Specification — https://www.w3.org/TR/WCAG22/
- WCAG 2.2 Understanding - Link Purpose — https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-link-only.html
- CommonMark Specification — https://spec.commonmark.org/
- GitHub Flavored Markdown — https://github.github.com/gfm/
- markdownlint Rules — https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md
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. You do not audit web UI components, HTML, CSS, or Office documents. For those, hand off to the appropriate wizard.
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.
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.
- yesterday First seen · 397 lines · 129 tokens per session scan A eea7a654db68
markdown-a11y-assistant is an agent published in the GitHub repository Community-Access/accessibility-agents (403 stars, last pushed 20d ago), licensed MIT. It adds 129 tokens to every session and 3,601 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 agents, from other repositories
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
flutter-reviewer
Read-only Flutter code reviewer. Dispatch after writing or changing Dart code to review changed code against VGV bloc, testing, security, and accessibility standards. Never edits files.
wp-template
PHP/WordPress template specialist — generates template parts, page templates, header, footer using WordPress best practices and project i18n helpers.
migrate-to-skeleton
Migrates a legacy KoliBri web component to the Skeleton Blueprint architecture (layered controller/FC/props pattern).
wp-audit-practices
WordPress coding standards auditor — escaping, sanitization, enqueueing, theme supports, hooks, i18n, code quality.
writer-publisher
Multilingual writing and publishing agent. Produces documentation, articles, reports, and web content in multiple languages, styles, tones, and formats. Use for any content authoring, editing, translation, or publishing task.