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/charlesjones-dev/claude-code-plugins-dev/accessibility-auditnpx skills add charlesjones-dev/claude-code-plugins-dev --skill accessibility-auditgit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWhat 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.00021 | $0.07801 |
| Opus 5 | $0.00010 | $0.03900 |
| Sonnet 5 | $0.00004 | $0.01560 |
| Haiku 4.5 | $0.00002 | $0.00780 |
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 2d 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.
- 2d 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 (34 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 7,801 once invoked, about $0.0001 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
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
gstack-openclaw-office-hours
Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
hallmark
Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.
design-system-builder
Extract design systems from reference UI images and generate implementation-ready UI design prompts. Use when users provide UI screenshots/mockups and want to create consistent designs, generate design systems, or build MVP UIs matching reference aesthetics.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.