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/skills-il/developer-tools/wcag-accessibility-widgetnpx skills add skills-il/developer-tools --skill wcag-accessibility-widgetgit clone --depth 1 https://github.com/skills-il/developer-toolsWrote 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/skills-il/developer-tools/wcag-accessibility-widget)<a href="https://agentmods.dev/skills/skills-il/developer-tools/wcag-accessibility-widget"><img src="https://agentmods.dev/badge/skills/skills-il/developer-tools/wcag-accessibility-widget.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 | $0.00165 | $0.02465 |
| Opus 5 | $0.00082 | $0.01233 |
| Sonnet 5 | $0.00033 | $0.00493 |
| Haiku 4.5 | $0.00016 | $0.00247 |
Grade A, and why
wcag-accessibility-widget 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 4d 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.
This is a copy
95% identical to wcag-accessibility-widget — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WCAG Accessibility Widget
Overview
A self-hosted floating accessibility widget: a fixed button that opens a panel with toggles for common WCAG 2.1 AA features. Settings are persisted in localStorage and applied as CSS classes on <html>. No third-party service needed.
WCAG 2.1 AA Checklist — What to Build
Before touching any component, audit these items first:
| Item | What to check / implement |
|---|---|
| Skip link | <a href="#main-content"> in layout, visually hidden, visible on focus. Target <main id="main-content" tabIndex={-1}> |
| Alt text | Every <img> has descriptive alt. Decorative images get alt="" + aria-hidden="true" |
| Color contrast | Normal text ≥ 4.5:1, large text ≥ 3:1. Common fail: text-gray-500 on dark bg (~3.9:1) → use text-gray-400 |
| Keyboard navigation | All interactive elements reachable by Tab. Test with keyboard only |
| ARIA labels | aria-label on icon-only buttons, aria-expanded on toggles, aria-label on <nav> when multiple navs exist |
| Decorative elements | Emoji, underline spans, SVG icons with adjacent text → aria-hidden="true" |
| Lang + dir | <html lang="he" dir="rtl"> (or your locale) on the root element |
| Mobile responsive | Site usable on mobile without horizontal scroll |
| Accessibility declaration | Required by Israeli law (חוק שוויון זכויות) — page at /accessibility |
| Privacy policy | a /privacy-policy page listing exactly what data the form collects |
Widget Architecture
1. Settings type + CSS class map
type Settings = {
keyboardNav: boolean;
noAnimations: boolean;
highContrast: boolean;
textLarge: boolean; // mutually exclusive with textSmall
textSmall: boolean;
readableFont: boolean;
markHeadings: boolean;
markLinks: boolean;
};
const CLASS_MAP: Record<keyof Settings, string> = {
keyboardNav: "a11y-keyboard",
noAnimations: "a11y-no-anim",
highContrast: "a11y-contrast",
textLarge: "a11y-font-lg",
textSmall: "a11y-font-sm",
readableFont: "a11y-readable",
markHeadings: "a11y-headings",
markLinks: "a11y-links",
};
What ships with it
5 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.
- 4d ago First seen · 245 lines · 165 tokens per session scan A ddc086a7c38f
wcag-accessibility-widget is a skill published in the GitHub repository skills-il/developer-tools (10 stars, last pushed 2d ago), licensed MIT. It adds 165 tokens to every session and 2,465 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to wcag-accessibility-widget, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
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…
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
可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.
waitlist-page
【模板: 等候名单页 / Waitlist】 【意图】为新产品 / 早鸟内测做一张极简等候页。 【布局】.
design-frontend-dev
Clean Impeccable frontend design skill. Use when the user wants to design, redesign, critique, audit, polish, harden, optimize, adapt, clarify, colorize, animate, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, onboarding, empty states…