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 jnPiyush/AgentX --skill accessibilitygit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/accessibility)<a href="https://agentmods.dev/skills/jnpiyush/agentx/accessibility"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/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/jnpiyush/agentx/accessibility"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/accessibility.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.00078 | $0.01669 |
| Opus 5.5 | $0.00031 | $0.00668 |
| Sonnet 5.5 | $0.00016 | $0.00334 |
| Haiku 4.5 | $0.00008 | $0.00167 |
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 1mo 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility
WHEN: A prototype, component, or page must meet WCAG 2.1 AA before review or release. This skill is the canonical Frontier a11y checklist; the prototype-audit skill consumes it mechanically.
When to Use This Skill
- Authoring a UX prototype that will be reviewed against WCAG 2.1 AA
- Reviewing PR diffs that change interactive UI
- Running the prototype-auditor pass 1 (Accessibility)
- Writing a11y acceptance criteria into a Story or PRD
Authoritative Sources
| Source | What it covers |
|---|---|
| W3C WCAG 2.1 (Web Content Accessibility Guidelines) | Normative success criteria |
| W3C ARIA Authoring Practices Guide (APG) | Widget patterns and keyboard interaction |
| MDN Accessibility Reference | Element and attribute behavior |
| WebAIM Contrast Checker | Numerical contrast ratios |
| axe-core rule catalogue | Mechanically verifiable subset |
Read the official spec before invoking judgement. Do not rely on training data for ARIA roles.
POUR Checklist
Perceivable
- Every meaningful image, SVG, or canvas has descriptive
alttext. Decorative images usealt=""and are removed from the accessibility tree. - Text contrast is at least 4.5:1 for body text and 3:1 for large text (>=24px regular or >=18.66px bold).
- Information is never conveyed by color alone. Status uses icon + label + color, not color only.
- Text can be resized to 200% without loss of content or function.
- Translucent surfaces (glass, frosted overlays) still meet contrast against the worst-case background. Provide a solid fallback when
backdrop-filteris unsupported. - Form fields have visible, persistent labels. Placeholders are not labels.
Operable
- Every interactive element reachable by mouse is reachable by keyboard.
- Focus indicators are visible with at least 3:1 contrast against adjacent colors and are not removed by
outline: nonewithout a replacement. - Tab order matches visual order. No positive
tabindexvalues. - A "Skip to main content" link is the first focusable element on every page.
- No keyboard traps. Modal dialogs trap focus only while open and restore focus on close.
- Touch targets are at least 44x44 CSS pixels.
- Drag, swipe, and other pointer gestures have a single-pointer or keyboard alternative.
- Time-limited interactions can be extended, paused, or disabled.
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.
- 1mo ago Changed b256dcea44ab
- 1mo ago First seen · 136 lines · 78 tokens per session scan A f77086b55303
accessibility is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,669 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…