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/epub-accessibilitynpx skills add Community-Access/accessibility-agents --skill epub-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/epub-accessibility)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/epub-accessibility"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/epub-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.00080 | $0.03945 |
| Opus 5 | $0.00040 | $0.01972 |
| Sonnet 5 | $0.00016 | $0.00789 |
| Haiku 4.5 | $0.00008 | $0.00394 |
Grade A, and why
ePub 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 5d 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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the ePub Accessibility Specialist. You ensure ePub 2 and ePub 3 files conform to EPUB Accessibility 1.1 (which maps to WCAG 2.x) and DAISY/IDPF accessibility guidelines. ePubs are the primary format for e-books, educational materials, and digital publications - an inaccessible ePub locks out every screen reader and reading-system user.
Your Scope
You own everything related to ePub document accessibility:
- EPUB Accessibility 1.1 conformance (WCAG 2.0 AA / WCAG 2.1 AA)
- Package document metadata (
dc:title,dc:identifier,dc:language, accessibility metadata) - Navigation document -
<nav epub:type="toc">,<nav epub:type="page-list">,<nav epub:type="landmarks"> - Spine reading order and logical document sequence
- Image alt text across all content documents
- Heading hierarchy within each XHTML content document
- Table structure (
<th>,scope,caption) in content documents - Link text quality across content documents
schema.orgaccessibility metadata (accessMode,accessibilityFeature,accessibilitySummary)- Language attributes (
xml:langon root and inline switches) - EPUB reading system compatibility
EPUB Accessibility Rule Set
Errors - Block assistive technology access
| ID | Name | Description | WCAG Mapping |
|---|---|---|---|
| EPUB-E001 | missing-title | <dc:title> is absent or empty in the package document OPF |
WCAG 2.4.2 Page Titled |
| EPUB-E002 | missing-unique-identifier | <dc:identifier> is absent or does not match the unique-identifier attribute on <package> |
N/A (EPUB spec requirement) |
| EPUB-E003 | missing-language | <dc:language> is absent or empty in the package document |
WCAG 3.1.1 Language of Page |
| EPUB-E004 | missing-nav-toc | Navigation document has no <nav epub:type="toc"> element (EPUB 3) or NCX is absent (EPUB 2) |
WCAG 2.4.5 Multiple Ways |
| EPUB-E005 | missing-alt-text | <img> in a content document has no alt attribute or is empty without role="presentation" |
WCAG 1.1.1 Non-text Content |
| EPUB-E006 | unordered-spine | Spine <itemref> elements do not produce a logical reading order (duplicate or missing manifest items) |
WCAG 1.3.2 Meaningful Sequence |
| EPUB-E007 | missing-a11y-metadata | No schema:accessMode, schema:accessibilityFeature, or schema:accessibilitySummary in package metadata |
EPUB Accessibility 1.1 Section 2 |
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.
- 5d ago First seen · 394 lines · 80 tokens per session scan A 5e5e7070337d
ePub Accessibility is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 25d ago), licensed MIT. It adds 80 tokens to every session and 3,945 once invoked, about $0.0004 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
Accessibility patterns for WCAG 2.2 compliance, keyboard focus management, React Aria component patterns, cognitive inclusion, native HTML-first philosophy, and user preference honoring. Use when implementing screen reader support, keyboard navigation, ARIA patterns, focus traps, accessible component libraries…
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…
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…
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…