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 skills add Community-Access/accessibility-agents --skill kb-open-source-accessibility-frameworkgit 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/kb-open-source-accessibility-framework)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/kb-open-source-accessibility-framework"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/kb-open-source-accessibility-framework/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/skills/community-access/accessibility-agents/kb-open-source-accessibility-framework"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/kb-open-source-accessibility-framework.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.00031 | $0.03497 |
| Opus 5.5 | $0.00012 | $0.01399 |
| Sonnet 5.5 | $0.00006 | $0.00699 |
| Haiku 4.5 | $0.00003 | $0.00350 |
Grade A, and why
kb-open-source-accessibility-framework 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 today.
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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reference data for the Open Source Accessibility Framework (OSAF). Open this when a task names the framework, one of its phases or actions, the tracking issue, or the project board, and you need the facts rather than a guess: which action an ID belongs to, its cadence, which phase skill implements it, or how registration works. The four phase skills carry the Definitions of Done; this file is the index above them.
What the framework is
The Open Source Accessibility Framework helps open source projects make accessibility part of how the project works, one practical step at a time. It is released under the MIT license (copyright GitHub, Inc.), hosted by the open-source-accessibility organization and sponsored by GitHub and Microsoft, at open-source-accessibility.github.io, with source in open-source-accessibility/Open-Source-Accessibility-Framework.
It is an improvement framework, not a certification, score or ranking. A project that participates is making its accessibility work public and trackable, not claiming to be accessible. Every skill in this package that touches the framework holds to that.
- Say: the framework supports steady, visible improvement; projects start small and adapt the actions; progress and remaining barriers are visible; automated checks supplement manual testing and community feedback.
- Never say: a project is certified, compliant or fully accessible because it participates; completing the framework guarantees conformance with any standard; automated testing finds every barrier; AI output replaces accessibility expertise or feedback from people with disabilities.
Phases and outcomes
The four phases, the outcome each one aims at, and the skill in this package that implements it. The framework lists them in this order; when a user says "phase 1" or "phase 3" they mean this order, but the framework itself does not number phases.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 250 lines · 31 tokens per session scan A fc273035f560
kb-open-source-accessibility-framework is a skill published in the GitHub repository Community-Access/accessibility-agents (429 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 3,497 once invoked, about $0.0001 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-10-29.
Other skills, from other repositories
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…
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-commerce
Make your store usable by everyone with WCAG 2.1 AA compliance — screen reader support, keyboard navigation, and accessible cart and checkout flows.
accessibility-expert
Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…
monochrome
Build accessible UI with monochrome, the framework-agnostic UI library for agents. Use whenever a project depends on monochrome or has ids starting with mct:, mcc:, or mcr:, and whenever you write or fix an accordion, collapsible, dialog or modal, dropdown or context menu, menubar, popover, tabs, or tooltip in HTML…