Borrowing it
Nothing to install: this file belongs to timothywarner-org/context-engineering. 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/timothywarner-org/context-engineering/main/.claude/agents/markdown-accessibility-specialist.mdgit clone --depth 1 https://github.com/timothywarner-org/context-engineeringWrote 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/timothywarner-org/context-engineering/markdown-accessibility-specialist)<a href="https://agentmods.dev/agents/timothywarner-org/context-engineering/markdown-accessibility-specialist"><img src="https://agentmods.dev/badge/agents/timothywarner-org/context-engineering/markdown-accessibility-specialist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/timothywarner-org/context-engineering/markdown-accessibility-specialist"><img src="https://agentmods.dev/badge/agents/timothywarner-org/context-engineering/markdown-accessibility-specialist.svg" alt="Reviewed on agentmods" width="80" 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.00392 | $0.05708 |
| Opus 5.5 | $0.00157 | $0.02283 |
| Sonnet 5.5 | $0.00078 | $0.01142 |
| Haiku 4.5 | $0.00039 | $0.00571 |
Grade A, and why
markdown-accessibility-specialist 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 2mo 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 — 407 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialized markdown accessibility expert focused on making documentation inclusive and accessible to all users. Your expertise is grounded in GitHub's '5 tips for making your GitHub profile page accessible' (https://github.blog/developer-skills/github/5-tips-for-making-your-github-profile-page-accessible/) and combines automated linting via markdownlint with deep accessibility judgment.
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.
- 2mo ago First seen · 407 lines · 392 tokens per session scan A b8a2bf6a5859
markdown-accessibility-specialist is an agent published in the GitHub repository timothywarner-org/context-engineering (27 stars, last pushed 1mo ago), licensed MIT. It adds 392 tokens to every session and 5,708 once invoked, about $0.0016 per session on Opus 5.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
engram:memory-review
Review and curate memory suggestions from Engram's review queue.
research-formatter
Composes the canonical Markdown report from claim-sliced research state. Owns report structure, prose, citation rendering, section metadata, assembly, and formatter audit for Phase 6.
research-collector
Collects web and document evidence using format-gated Docling SDK with persistent DocumentConverter and version-scoped cache; per-host semaphore with stepped active backoff; Retry-After honored; coherent header rotation (web crawl only); same-site Referer policy; manifested staging-index resume. Resolves tool paths…
research-synthesizer
Extracts canonical claims, graph relationship metadata, section briefs, and per-section claim slices.
research
Orchestrates research pipeline phases, spawns collector and synthesizer agents, manages checkpoints and manifest state.
network-architect
Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.