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 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/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/cognitive-accessibility"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/cognitive-accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 58 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
- medium Agent Snooping · line 5 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00024 | $0.01267 |
| Opus 5.5 | $0.00010 | $0.00507 |
| Sonnet 5.5 | $0.00005 | $0.00253 |
| Haiku 4.5 | $0.00002 | $0.00127 |
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 27d 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 — 142 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 3 - COGA Guidance Assessment
Beyond WCAG, assess alignment with COGA's "Making Content Usable" guidance. These are best-practice recommendations, not hard technical requirements.
Plain Language
Review all instructional text, error messages, tooltips, and UI copy:
- Short sentences. Flag any sentence exceeding 25 words. Aim for 15-20 words.
- Active voice. Flag passive constructions ("The form was submitted" -> "You submitted the form").
- Common words. Flag technical jargon, Latin abbreviations (e.g., "i.e.", "viz."), legalistic phrasing.
- Positive phrasing. Flag double negatives ("not unable to" -> "able to").
- Consistent terminology. Flag using multiple terms for the same concept ("sign in" and "log in" on the same page).
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.
- 27d ago Changed · -86 lines · +21 tokens per session b9a50f2b2397
- 1mo 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 (427 stars, last pushed 27d ago), licensed MIT. It adds 24 tokens to every session and 1,267 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-08-30.
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…
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…
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…
Modern Web Accessibility for Interactive UI
An accessibility review for interactive interface elements such as dialogs, menus, popovers, tabs, forms, and live updates.
a11y-toolkit
Use for ALL accessibility work — WCAG 2.2 audits of URLs or HTML, real rendered contrast checks (including text over images, pixel-level), color-pair contrast and nearest passing color, European Accessibility Act / RD 1112/2018 accessibility statements, pre-deploy regression detection (accessible names, tab order)…
validate-motion
Browse MotionSpec motion primitives and draft or validate a MotionSpec JSON specification for web animation. Use for catalog questions, choosing an available primitive, or checking an existing spec. This workflow validates specifications; it does not compile, deploy or execute animation.