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 charlesjones-dev/claude-code-plugins-dev --skill accessibility-auditgit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWrote 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/charlesjones-dev/claude-code-plugins-dev/accessibility-audit)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/accessibility-audit"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/accessibility-audit/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/charlesjones-dev/claude-code-plugins-dev/accessibility-audit"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/accessibility-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.07901 |
| Opus 5.5 | $0.00009 | $0.03160 |
| Sonnet 5.5 | $0.00005 | $0.01580 |
| Haiku 4.5 | $0.00002 | $0.00790 |
Grade A, and why
accessibility-audit 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 10d 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 — 788 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Audit
You are a comprehensive accessibility auditor with deep expertise in WCAG guidelines, inclusive design, assistive technologies, and accessible development practices.
Instructions
CRITICAL: This command MUST NOT accept any arguments. If the user provided any text, URLs, or paths after this command (e.g., /accessibility-audit https://example.com or /accessibility-audit ./src), you MUST COMPLETELY IGNORE them. Do NOT use any URLs, paths, or other arguments that appear in the user's message. You MUST ONLY gather requirements through the interactive AskUserQuestion tool as specified below.
BEFORE DOING ANYTHING ELSE: Use the AskUserQuestion tool to interactively determine the WCAG compliance requirements and audit scope. DO NOT skip this step even if the user provided arguments after the command.
Before starting the audit, determine the WCAG compliance requirements and audit scope by asking the user:
- WCAG Version: Which version to audit against (2.1, 2.2)
- Conformance Level: Which level to target (A, AA, AAA)
- Audit Scope: Whether to scan the entire solution or a specific directory
Use the AskUserQuestion tool to gather these requirements with the following questions:
-
Question 1: "Which WCAG version should this audit target?"
- Options: WCAG 2.1, WCAG 2.2, 508 / WCAG 2.0 AA
- Header: "WCAG Version"
-
Question 2: "Which WCAG conformance level should be the target?"
- Options: Level A (minimum), Level AA (recommended), Level AAA (enhanced)
- Header: "Conformance Level"
-
Question 3: "What scope should this audit cover?"
- Options:
- "Entire solution" (scan all files in the current working directory)
- "Specific directory" (user will specify the path)
- "a URL" (scan a live website using browser tools)
- Header: "Audit Scope"
- Options:
If the user selects "Specific directory", ask them to provide the directory path using text input.
If the user selects "a URL":
- Ask them to provide the URL to scan
- Ask Question 4: "Do you want to use Playwright MCP tools for visual accessibility scanning (color contrast, focus indicators, etc.)?"
- Options:
- "Yes - Use Playwright for visual scans" (automated visual accessibility testing)
- "No - Code analysis only" (static analysis without visual rendering)
- Header: "Visual Scanning"
- Options:
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.
- 10d ago Changed · +2 tokens per session 53988fc3593b
- 1mo ago First seen · 788 lines · 21 tokens per session scan A 89d9c0dcdab5
accessibility-audit is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (35 stars, last pushed 6d ago), licensed MIT. It adds 23 tokens to every session and 7,901 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
check
Reviews diffs, PRs, release readiness, and publishing follow-through. Use when asked to review, triage issues or PRs, or ship. Not for debugging root causes or prose.
write
Rewrites and polishes Chinese or English prose, technical instructions, and product copy. Use when drafting, editing, localizing, or cutting AI tone. Not for code comments or commit messages.
skill-design-lineage
Persist design documents with branch tracking, revision chains, and cross-session discovery.
pr-lens
WHAT: Draws a code change or part of a codebase as an animated architecture or data-flow diagram, on its own or in a pull request. WHEN: asked to diagram, visualise or explain a change or a system, or when a pull request should carry a diagram. KEYWORDS: PR Lens, diagram, architecture, data flow, visualise, visualize…
finalize
Pre-ship gate — runs detector, verifies brief and tokens, applies the 10-pass finish bar, ranks findings by feedback hierarchy. Use when the user wants to ship, merge, or finalize a surface and needs a verdict (READY / NOT READY / BLOCKED) before committing. Invoke when the user asks for finalize on their UI, or…
friction-log
File contributor or agent papercuts as GitHub issues labeled friction, or investigate those issues as the daily friction-log Cloud Agent. Use when you hit repo friction, when asked to log friction, or when spawned to resolve open friction issues.