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 varutasu/agent-pipeline --skill accessibility-auditgit clone --depth 1 https://github.com/varutasu/agent-pipelineWrote 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/varutasu/agent-pipeline/accessibility-audit)<a href="https://agentmods.dev/skills/varutasu/agent-pipeline/accessibility-audit"><img src="https://agentmods.dev/badge/skills/varutasu/agent-pipeline/accessibility-audit.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.1 | $0.00000 | $0.02856 |
| Opus 5 | $0.00000 | $0.01428 |
| Sonnet 5 | $0.00000 | $0.00571 |
| Haiku 4.5 | $0.00000 | $0.00286 |
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 8d 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.
name: accessibility-audit
description: >-
Run a WCAG 2.2 accessibility audit on a UI change or surface. Produces a
severity-ranked findings report keyed to WCAG success criteria, with code
diffs for the fixable cases. Use when role-a11y-auditor is invoked, when
the user asks for an a11y review, before shipping a UI convoy, or whenever
a change touches anything interactive (forms, navigation, modals, dynamic
content, media). Skip if skip: a11y is set in the convoy or the change is
server/infra-only.
Accessibility audit
Five-layer audit framework keyed to WCAG 2.2 (W3C, October 2023). Outputs a severity 0–4 findings list, an executive summary, and code-diff suggestions for fixable issues. The default rubric below covers the cases that actually fail in production; the deep reference at references/wcag-2.2-checklist.md covers all 86 success criteria for completeness.
When to invoke
- Automatic: by
role-a11y-auditorwhen a convoy's PR draft touchesapp/**,components/**, or any UI surface. - Manual: when the user says "audit this for a11y", "check accessibility", "can a screen reader use this", or names a WCAG criterion (
2.1.1,1.4.3, etc.). - Pre-merge: when an audit fan-out runs (
/multitask role-reviewer + role-security-auditor + role-design-system-auditor + role-a11y-auditorper the multitask playbook).
Severity scale
| Severity | Meaning | Treatment |
|---|---|---|
| 4 — Blocker | WCAG Level A failure on a critical path (auth, checkout, primary navigation). Users on AT cannot complete the journey. | Block merge. File as a child task under the audit document (per Phase 2b). |
| 3 — Major | WCAG Level AA failure, or Level A failure on a non-critical path. AT users hit a workaround or degraded experience. | File as child task. Strongly recommend fix before merge. |
| 2 — Moderate | WCAG Level AAA failure, or AA on a low-traffic surface, or AT-specific friction not codified in WCAG (e.g. confusing announcement order). | Inline in audit doc; create task only if pattern repeats. |
| 1 — Minor | Polish item: improved labels, redundant ARIA cleanup, focus order optimization. | Inline only. |
| 0 — Info | Note for the maintainer; not a defect. | Inline only. |
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.
- 8d ago First seen · 136 lines · 0 tokens per session scan A 3e6626a73815
accessibility-audit is a skill published in the GitHub repository varutasu/agent-pipeline (2 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,856 tokens. 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-31.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…