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 Lrinvl1203/world-class-web-design-os --skill a11y-performancegit clone --depth 1 https://github.com/Lrinvl1203/world-class-web-design-osWrote 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/lrinvl1203/world-class-web-design-os/a11y-performance)<a href="https://agentmods.dev/skills/lrinvl1203/world-class-web-design-os/a11y-performance"><img src="https://agentmods.dev/badge/skills/lrinvl1203/world-class-web-design-os/a11y-performance/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/lrinvl1203/world-class-web-design-os/a11y-performance"><img src="https://agentmods.dev/badge/skills/lrinvl1203/world-class-web-design-os/a11y-performance.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.00056 | $0.00293 |
| Opus 5 | $0.00028 | $0.00147 |
| Sonnet 5 | $0.00011 | $0.00059 |
| Haiku 4.5 | $0.00006 | $0.00029 |
Grade A, and why
a11y-performance 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 12d 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.
What it actually says
Accessibility + Performance
Accessibility baseline
Target WCAG 2.2 AA for production work unless the project specifies a higher standard.
Check at minimum:
- semantic landmarks/headings/controls and accessible names;
- keyboard order and operation;
- visible focus and focus not fully obscured by authored sticky/fixed content;
- contrast/non-text contrast as applicable;
- pointer target sizing/spacing;
- non-drag alternative for drag interactions where required;
- labels, errors and status communication;
- reduced-motion behavior;
- zoom/reflow and narrow-width usability;
- media alternatives where applicable.
Read references/gates.md for numerical gates.
Performance
Protect the user path before decorative fidelity:
- responsive/compressed images and reserved aspect ratios;
- font subset/weight discipline;
- lazy loading of noncritical creative code;
- animation of compositor-friendly properties when possible;
- no heavy JS work in scroll handlers;
- cap DPR/effects for 3D and stop offscreen render loops;
- avoid duplicated animation/component packages.
Measure rather than infer when a runnable app is available.
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.
- 12d ago First seen · 40 lines · 56 tokens per session scan A f5c8bbbabd43
a11y-performance is a skill published in the GitHub repository Lrinvl1203/world-class-web-design-os (8 stars, last pushed 15d ago), licensed MIT. It adds 56 tokens to every session and 293 once invoked, about $0.0003 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-31.
Other skills, from other repositories
responsive-ui-qa
Inspect, diagnose, fix, and verify responsive frontend defects across routes, states, containers, and input modes. Use for mobile or desktop QA, overflow, overlap, broken navigation, unstable grids, clipped text, blank media, viewport regressions, screenshot comparison, and post-implementation visual verification.
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
storybook-mcp-integration
Reference for the Storybook MCP server itself (@storybook/addon-mcp): 6 tools across 3 toolsets (dev, docs, testing), availability detection, and per-agent toolset filtering. Use when setting up the server or calling these tools directly against components that already exist. For the end-to-end pipeline that turns a…
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
Axe-core Accessibility Testing
Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.