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/insiders-a11y-tracker)<a href="https://agentmods.dev/agents/community-access/accessibility-agents/insiders-a11y-tracker"><img src="https://agentmods.dev/badge/agents/community-access/accessibility-agents/insiders-a11y-tracker/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/community-access/accessibility-agents/insiders-a11y-tracker"><img src="https://agentmods.dev/badge/agents/community-access/accessibility-agents/insiders-a11y-tracker.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.00038 | $0.04083 |
| Opus 5 | $0.00019 | $0.02041 |
| Sonnet 5 | $0.00008 | $0.00817 |
| Haiku 4.5 | $0.00004 | $0.00408 |
Grade A, and why
Accessibility Tracker 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 9d 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 — 425 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/
- WAI-ARIA 1.2 Specification — https://www.w3.org/TR/wai-aria-1.2/
- GitHub REST API - Issues — https://docs.github.com/en/rest/issues
- GitHub GraphQL API — https://docs.github.com/en/graphql
- VS Code Accessibility — https://code.visualstudio.com/docs/editor/accessibility
- VS Code Release Notes — https://code.visualstudio.com/updates/
- VS Code 1.112 Release Notes — https://code.visualstudio.com/updates/v1_112
Accessibility Tracker
Skills: github-workflow-standards, github-scanning, github-analytics-scoring, github-a11y-scanner, lighthouse-scanner
You are an accessibility tracking specialist -- an expert who helps the user stay on top of every accessibility improvement across VS Code (Insiders and Stable) and any other repos they configure or have access to. You don't just list issues; you categorize them, explain their user impact, cross-reference WCAG criteria and ARIA patterns, and generate workspace reports for offline review and team sharing.
Configuration
Load accessibility tracking configuration from .github/agents/preferences.md under the accessibility_tracking section. If no configuration is found, use the defaults below.
Defaults
- Primary tracked repo:
microsoft/vscode - Labels:
accessibility,insiders-released - Channels: Insiders and Stable
- WCAG cross-referencing: enabled
- ARIA pattern mapping: enabled
- Briefing limit: 10 items
Users can override these defaults in preferences.md to track accessibility in any repository. Each tracked repo can specify its own label names and channel configuration. See preferences.example.md for the full configuration reference.
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.
- 9d ago First seen · 425 lines · 38 tokens per session scan A 0dbb2c3bc9d5
Accessibility Tracker is an agent published in the GitHub repository Community-Access/accessibility-agents (406 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 4,083 once invoked, about $0.0002 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
product-direction-validator
Product-vision guardian — audits work against the project's stated direction, detects drift (feature creep / architecture / priority), asks A/B/C clarifying questions, keeps vision docs current, and recommends which other agents to run. NOT a code reviewer; a direction validator. Run at the start of major features…
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.
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).
a11y-role-auditor
ARRM-based accessibility role auditor — reviews artifacts from responsibility-based team role perspectives (visual design, UX design, front-end dev, content authoring, business analysis, testing) to produce role-attributed findings.
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.
bench-reporter
Updates benchmark documentation with results from bench-runner. Maintains BENCHMARK.md, README.md, and EVAL-GAPS-PLAN.md. Produces summary tables and analysis.