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 skills/community-access/accessibility-agents/ci-accessibilitynpx skills add Community-Access/accessibility-agents --skill ci-accessibilitygit 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/skills/community-access/accessibility-agents/ci-accessibility)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/ci-accessibility"><img src="https://agentmods.dev/badge/skills/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 | $0.00056 | $0.00349 |
| Opus 5 | $0.00028 | $0.00175 |
| Sonnet 5 | $0.00011 | $0.00070 |
| Haiku 4.5 | $0.00006 | $0.00035 |
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 4d 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.
What it actually says
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 for accessibility scanning
- Manage baselines (
axe-baseline.json) so CI only fails on regressions - Configure thresholds for severity-based gating
- SARIF integration for GitHub code scanning
- PR annotations with pass/fail summaries
- Multi-platform support (GitHub Actions, Azure DevOps, GitLab CI, CircleCI, Jenkins)
Workflow
Phase 1 — Assess
Check for existing CI config, accessibility tooling, baseline files, and scan configuration.
Phase 2 — Configure
Determine CI platform, scanning tool (axe-core CLI, Playwright+axe, Lighthouse CI), gating strategy (strict/standard/baseline), and output format (SARIF, PR comment, artifact).
Phase 3 — Generate
Create CI config with WCAG 2.2 AA tags, baseline comparison, SARIF output, and pass/fail summary.
Phase 4 — Baseline Management
- Create baseline from current violations
- CI compares new scans against baseline
- Only new violations fail — existing baseline issues don't block
- Update baseline after fixes to lock in improvements
Phase 5 — Verify
Run pipeline in a test PR, document for the team, offer scheduled scans.
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.
- 4d ago First seen · 36 lines · 56 tokens per session scan A ceb00263643b
CI Accessibility is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 23d ago), licensed MIT. It adds 56 tokens to every session and 349 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-08-30.
Other skills, from other repositories
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
game-accessibility-engineer
!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat…
accessibility-engineer
You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…
wcag-accessibility
Apply and audit WCAG 2.2 accessibility standards when building or testing frontend components. ALWAYS use this skill when: building any UI component, page, or layout (even if the user doesn't mention accessibility); running accessibility audits or tests; asked to "check a11y", "test accessibility", "audit WCAG…