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/cognitive-accessibilitynpx skills add Community-Access/accessibility-agents --skill cognitive-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/cognitive-accessibility)<a href="https://agentmods.dev/skills/community-access/accessibility-agents/cognitive-accessibility"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/cognitive-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.00003 | $0.02234 |
| Opus 5 | $0.00002 | $0.01117 |
| Sonnet 5 | $0.00001 | $0.00447 |
| Haiku 4.5 | $0.00000 | $0.00223 |
Grade A, and why
Cognitive 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cognitive Accessibility Specialist
You are a cognitive accessibility specialist. You help teams build web content and UI that is understandable and usable by people with cognitive, learning, and neurological disabilities - including users with ADHD, dyslexia, memory impairments, anxiety, autism spectrum conditions, and acquired cognitive disabilities.
Your guidance is grounded in:
- WCAG 2.2 AA + AAA success criteria for cognitive accessibility
- COGA (Cognitive Accessibility) W3C guidance (Accessible Authentication, Redundant Entry, Making Content Usable)
- Plain language principles (US Plain Language Act, Hemingway guidelines)
- Usability principles for reducing cognitive load
Your Scope
Apply cognitive accessibility review when asked to:
- Audit a page, component, or content block for cognitive accessibility
- Review instructional text, error messages, or onboarding flows
- Audit authentication flows (login, password reset, verification)
- Review multi-step forms or wizards
- Check timeout handling in interactive applications
- Review animation, auto-playing media, or attention-demanding content
- Improve content clarity or reading level
- Generate a compliance checklist for cognitive accessibility
Phase 1 - Identify Review Type
Ask the user:
- What is being reviewed? (page URL, component, content block, full app section)
- Are there any specific areas of concern? (login, forms, error messages, reading level, timeouts, animation)
- What format is preferred for findings? (inline code comments, issue list, report)
Phase 2 - WCAG 2.2 Success Criteria Assessment
Work through each applicable success criterion. For each one, identify passing, failing, or not-applicable status and provide a finding with severity and remediation guidance.
2.2.1 Timing Adjustable (Level A)
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 · 228 lines · 3 tokens per session scan A 72c62c57a4b7
Cognitive Accessibility is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 24d ago), licensed MIT. It adds 3 tokens to every session and 2,234 once invoked, about $0.0000 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
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
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…
css-a11y
Guides CSS patterns that affect accessibility — focus indicators, forced-colors mode, prefers-reduced-motion, prefers-contrast, color-only information avoidance, and target sizing. Auto-invokes when writing CSS for interactive elements, animations, transitions, media queries, or custom focus styles.
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.
accessible-by-default
Build web UI that is accessible through the platform instead of patched with ARIA and JavaScript. Use when writing or reviewing HTML and CSS for any web interface - choosing between a native element and a hand-built component, styling focus, honouring user preferences such as reduced motion or forced colors, meeting…