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 RadOrigin-LLC/RAD-Claude-Skills --skill a11y-reviewgit clone --depth 1 https://github.com/RadOrigin-LLC/RAD-Claude-SkillsWrote 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/radorigin-llc/rad-claude-skills/a11y-review)<a href="https://agentmods.dev/skills/radorigin-llc/rad-claude-skills/a11y-review"><img src="https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/a11y-review/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/radorigin-llc/rad-claude-skills/a11y-review"><img src="https://agentmods.dev/badge/skills/radorigin-llc/rad-claude-skills/a11y-review.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.00161 | $0.06637 |
| Opus 5 | $0.00081 | $0.03318 |
| Sonnet 5 | $0.00032 | $0.01327 |
| Haiku 4.5 | $0.00016 | $0.00664 |
Grade A, and why
a11y-review 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.
How it starts
The opening of the file, as written. The whole thing — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Review (static analysis)
Perform a structured static analysis pass over the specified component, page, or codebase. Execute all eight phases in order and produce an actionable, severity-ranked report with each finding tagged by confidence level.
What this skill is — and what it isn't
This skill performs pattern-based static analysis over .tsx / .jsx / .astro / .html / .css source. It is not a WCAG audit, does not run axe-core, does not test runtime focus behavior, and does not test with screen readers. It does compute WCAG sRGB contrast ratios for Tailwind class pairs co-occurring on the same element (the check-tailwind-contrast.py validator), but it cannot see DOM-inherited backgrounds without runtime.
What this skill catches well (high confidence):
- Missing
alton<img>, missing<label>association, missing accessible name on icon buttons outline: none/outline-nonewithout a focus-visible replacement (Tailwind users — axe often misses this because it inspects computed styles)aria-hidden="true"on focusable elements or their ancestors- Hardcoded ARIA states (
aria-expanded="true"as a string literal, not driven by component state) <div onClick>/<span onClick>without role + keyboard handlers- Skipped heading levels, missing landmarks
- React-specific focus drift (modal close handlers without focus restoration)
- Color contrast for Tailwind class pairs on the same element —
check-tailwind-contrast.pycomputes real WCAG 2.x sRGB ratios from the Tailwind v3 default palette plus custom colors parsed fromtailwind.config.{js,ts,cjs,mjs}. Flags AA failures (4.5:1 body / 3:1 large or UI) and surfaces the actual computed ratio. Function-based palettes (colors imported from another file) are skipped with a warning.
What this skill flags but cannot confirm (medium confidence):
- Color contrast where the background comes from a DOM ancestor — the validator can't resolve inherited backgrounds across the rendered tree without a browser
- Color contrast involving alpha-blended (translucent) backgrounds — not handled by the validator
- ARIA state synchronization beyond the simplest cases
- Whether a
<fieldset>correctly wraps a logical group
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 · 450 lines · 161 tokens per session scan A faad14fa8d04
a11y-review is a skill published in the GitHub repository RadOrigin-LLC/RAD-Claude-Skills (5 stars, last pushed 26d ago), licensed Apache-2.0. It adds 161 tokens to every session and 6,637 once invoked, about $0.0008 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
light-dark-mode
Load this skill whenever the project supports light/dark mode, colour theme switching, high-contrast mode, or responds to prefers-color-scheme. Under no circumstances hard-code colours that break in alternative themes. Absolutely always test colour contrast in both light and dark themes, and respect user OS-level…
tables
Load this skill whenever the project contains HTML data tables ( elements). Under no circumstances use tables for layout purposes. Absolutely always include elements with appropriate scope attributes, a or aria-labelledby, and ensure complex tables have headers associated with data cells. Apply these rules to every…
Load this skill whenever the project includes print stylesheets, print media queries (@media print), or any content intended for physical printing. Under no circumstances omit print CSS that ensures readable, accessible printed output. Absolutely always hide decorative elements, expand link URLs, and maintain…
progressive-enhancement
Load this skill when building any web feature, reviewing architecture decisions, or evaluating JavaScript dependencies. Under no circumstances build features that break completely when JavaScript is unavailable or fails. Absolutely always start with semantic HTML, layer CSS enhancements, and add JavaScript as the…
wes-bos-sick-picks
Research-first workflow for building frontend UI components (any framework), in the spirit of Wes Bos. Use when designing or implementing a UI component, layout, interaction, or CSS/HTML feature and you want a modern, accessible, best-practice solution rather than a first guess. Researches pitfalls and platform…
generic-static-code-reviewer
Review static site code for bugs, security issues, performance problems, accessibility gaps, and CLAUDE.md compliance. Enforces pure HTML/CSS/JS standards, minimal page weight, mobile-first design. Use when completing features, before commits, or reviewing changes.