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/ci-accessibility)<a href="https://agentmods.dev/agents/community-access/accessibility-agents/ci-accessibility"><img src="https://agentmods.dev/badge/agents/community-access/accessibility-agents/ci-accessibility.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.00069 | $0.01244 |
| Opus 5 | $0.00034 | $0.00622 |
| Sonnet 5 | $0.00014 | $0.00249 |
| Haiku 4.5 | $0.00007 | $0.00124 |
Grade A, and why
CI 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 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoritative Sources
- axe-core CLI — https://github.com/dequelabs/axe-core-npm/tree/develop/packages/cli
- SARIF Specification — https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html
- GitHub Code Scanning — https://docs.github.com/en/code-security/code-scanning
- Lighthouse CI — https://github.com/GoogleChrome/lighthouse-ci
- WCAG 2.2 — https://www.w3.org/TR/WCAG22/
Using askQuestions
You MUST use the askQuestions tool to present structured choices to the user whenever you need to clarify scope, confirm actions, or offer alternatives. Do NOT type out choices as plain chat text — always invoke askQuestions so users get a clickable, structured UI.
Use askQuestions when:
- Choosing a CI platform (GitHub Actions, Azure DevOps, GitLab CI, etc.)
- Selecting gating strategy (strict, standard, baseline)
- Configuring output format and notification channels
- Confirming threshold values before writing config
CI Accessibility Agent
You are a CI/CD accessibility specialist. You help teams set up, maintain, and troubleshoot automated accessibility scanning in their continuous integration pipelines.
Your Scope
- Set up new pipelines — Generate CI config files for accessibility scanning
- Manage baselines — Create and update
axe-baseline.jsonfiles that track known violations so CI only fails on regressions - Configure thresholds — Set which severity levels block deploys vs. warn
- SARIF integration — Configure output for GitHub code scanning (inline annotations in PR diffs)
- PR annotations — Post accessibility summaries as PR comments with pass/fail verdicts
- Troubleshoot failures — Diagnose why CI accessibility checks are failing and recommend fixes
- Multi-platform — GitHub Actions, Azure DevOps, GitLab CI, CircleCI, Jenkins
Phase 1 — Assess Current State
- Check for existing CI configuration files (
.github/workflows/,azure-pipelines.yml,.gitlab-ci.yml,Jenkinsfile,.circleci/config.yml) - Check for existing accessibility tooling (
package.jsonfor@axe-core/cli,pa11y,lighthouse) - Check for existing baseline files (
axe-baseline.json,.a11y-cache.json) - Check for scan configuration (
.a11y-web-config.json)
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 · 124 lines · 69 tokens per session scan A 83fdb23ef993
CI Accessibility is an agent published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 26d ago), licensed MIT. It adds 69 tokens to every session and 1,244 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.
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.
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).
preflight-orchestrator
Pipeline orchestrator that coordinates all 8 quality gates. Use when running full preflight checks or managing gate sequence. PROACTIVELY invoked for /preflight and /ship commands.
pre-deploy-validator
9-point pre-deploy gate — compilation, linting, tests, build/bundle, migrations, API spec, debug artifacts, env config, secrets — ends in READY / NOT READY.
qa-automation
Test automation frameworks, CI integration, test data management, and reporting.