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/yonatangross/orchestkit/accessibilitynpx skills add yonatangross/orchestkit --skill accessibilitygit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/accessibility)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/accessibility"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/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.00065 | $0.02434 |
| Opus 5 | $0.00032 | $0.01217 |
| Sonnet 5 | $0.00013 | $0.00487 |
| Haiku 4.5 | $0.00006 | $0.00243 |
Grade A, and why
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 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility
Comprehensive patterns for building accessible web applications: WCAG 2.2 AA compliance, keyboard focus management, React Aria component patterns, native HTML-first philosophy, cognitive inclusion, and user preference honoring. Each category has individual rule files in rules/ loaded on-demand.
Quick Reference
| Category | Rules | Impact | When to Use |
|---|---|---|---|
| WCAG Compliance | 3 | CRITICAL | Color contrast, semantic HTML, automated testing |
| POUR Exit Criteria | 1 | CRITICAL | Falsifiable pass/fail thresholds for each WCAG 2.2 AA criterion |
| Static Anti-Patterns | 1 | HIGH | Grep-able patterns detectable without a browser |
| Focus Management | 1 | HIGH | Keyboard navigation; trap/restoration mechanics live upstream |
| React Aria | 2 | HIGH | Accessible components and form hooks; overlay APIs live upstream |
| Modern Web Accessibility | 2 | CRITICAL/HIGH | Native HTML first, user preferences; cognitive ceilings in references/ork-delta.md |
Total: 10 rules across 6 categories
Quick Start
// Semantic HTML with ARIA
<main>
<article>
<header><h1>Page Title</h1></header>
<section aria-labelledby="features-heading">
<h2 id="features-heading">Features</h2>
</section>
</article>
</main>
// Focus trap with React Aria
import { FocusScope } from 'react-aria';
<FocusScope contain restoreFocus autoFocus>
<div role="dialog" aria-modal="true">
{children}
</div>
</FocusScope>
WCAG Compliance
WCAG 2.2 AA implementation for inclusive, legally compliant web applications.
| Rule | File | Key Pattern |
|---|---|---|
| Color Contrast | ${CLAUDE_PLUGIN_ROOT}/skills/accessibility/rules/wcag-color-contrast.md |
4.5:1 text, 3:1 UI components, focus indicators |
| Semantic HTML | ${CLAUDE_PLUGIN_ROOT}/skills/accessibility/rules/wcag-semantic-html.md |
Landmarks, headings, ARIA labels, form structure |
| Testing | ${CLAUDE_PLUGIN_ROOT}/skills/accessibility/rules/wcag-testing.md |
axe-core, Playwright a11y, screen reader testing |
What ships with it
20 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.
- examples/wcag-examples.md 21 KB
- metadata.json 487 B
- references/ork-delta.md 3.4 KB
- references/ux-thresholds-quick.md 1.6 KB
- rules/_sections.md 2.2 KB
- rules/_template.md 339 B
- rules/a11y-antipatterns-static.md 4.0 KB
- rules/aria-components.md 5.7 KB
- rules/aria-forms.md 6.2 KB
- rules/focus-keyboard-nav.md 6.0 KB
- rules/pour-exit-criteria.md 4.9 KB
- rules/wcag-color-contrast.md 3.1 KB
- rules/wcag-native-html-first.md 4.0 KB
- rules/wcag-semantic-html.md 3.8 KB
- rules/wcag-testing.md 4.2 KB
- rules/wcag-user-preferences.md 3.6 KB
- scripts/accessible-component-template.tsx 11 KB
- scripts/accessible-form-template.tsx 15 KB
- scripts/focus-trap-template.tsx 13 KB
- test-cases.json 3.9 KB
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 · 179 lines · 65 tokens per session scan A 615168cdc376
accessibility is a skill published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 2,434 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 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-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-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…
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…