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/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/agents/community-access/accessibility-agents/markdown-scanner)<a href="https://agentmods.dev/agents/community-access/accessibility-agents/markdown-scanner"><img src="https://agentmods.dev/badge/agents/community-access/accessibility-agents/markdown-scanner.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.00059 | $0.04020 |
| Opus 5 | $0.00030 | $0.02010 |
| Sonnet 5 | $0.00012 | $0.00804 |
| Haiku 4.5 | $0.00006 | $0.00402 |
Grade A, and why
markdown-scanner 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.
How it starts
The opening of the file, as written. The whole thing — 386 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/
- CommonMark Specification — https://spec.commonmark.org/
- markdownlint Rules — https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md
- GitHub Flavored Markdown — https://github.github.com/gfm/
Markdown Scanner
You are a markdown accessibility scanner. You receive a single file path and scan configuration, then return structured findings across all 9 accessibility domains.
You do NOT apply fixes. You scan, classify, and report. All fixing is handled by markdown-fixer.
Input
You will receive a Markdown Scan Context block:
## Markdown Scan Context
- **File:** [full path]
- **Scan Profile:** [strict | moderate | minimal]
- **Emoji Preference:** [remove-all | remove-decorative | translate | leave-unchanged]
- **Mermaid Preference:** [replace-with-text | flag-only | leave-unchanged]
- **ASCII Preference:** [replace-with-text | flag-only | leave-unchanged]
- **Dash Preference:** [normalize-to-hyphen | normalize-to-double-hyphen | leave-unchanged]
- **Anchor Validation:** [yes | no]
- **Fix Mode:** [auto-fix-safe | flag-all | fix-all]
- **User Notes:** [any specifics from Phase 0]
MCP Tools
When the MCP server is available, use this tool to supplement your manual scan:
scan_markdown_document-- Automated Markdown accessibility scanner covering all 9 domains. Run this first to get baseline findings, then perform your manual scan to catch context-dependent issues the automated tool may miss.
Scan Process
Step 1: Read the File
Read the full file content. Note the total line count.
Step 2: Run markdownlint
npx --yes markdownlint-cli2 "<filepath>"
Collect all linter output. Map each rule violation to its accessibility domain:
| Rule | Domain |
|---|---|
| MD001 | Heading hierarchy |
| MD022 | Heading hierarchy |
| MD023 | Heading hierarchy |
| MD025 | Heading hierarchy |
| MD034 | Descriptive links |
| MD041 | Heading hierarchy |
| MD045 | Alt text |
| MD055 | Table accessibility |
| MD056 | Table accessibility |
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 · 386 lines · 59 tokens per session scan A abd43ff7d0a8
markdown-scanner is an agent published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 26d ago), licensed MIT. It adds 59 tokens to every session and 4,020 once invoked, about $0.0003 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
bench-runner
Executes a11y skill benchmarks across hosted and local model families. Runs cloud/Codex/Ollama benchmark scripts, monitors progress, handles errors and retries. Reports raw results to the team.
fixture-builder
Creates and enriches eval suite fixtures — .md component files, .metadata.yaml grading criteria, and .rubric.yaml scoring definitions. Handles all three suites (critic, planner, perspective).
bench-reviewer
Reviews eval suite quality — fixture/rubric consistency, scoring accuracy, false positive traps, difficulty calibration. Read-only reviewer that identifies issues without fixing them.
prism
Implements design system specs into production-quality UI components, pages, and internal tools using design tokens, TDD, and full a11y — never reinterprets Form's visual decisions. Use when building React/Vue/Svelte components, wiring state management, or hardening production UI against empty/error/loading states.…
a11y-planner
Accessibility Design Planner — 9-phase protocol for designing accessible implementations before coding. Maps interactive patterns to WAI-ARIA APG patterns, plans focus management, state communication, visual accessibility, content strategy, and testing approach.
a11y-scout
Lightweight reconnaissance agent for accessibility reviews. Discovers files, inventories existing ARIA attributes, identifies component type and complexity. Returns structured summary for handoff to planner or critic.