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 ThibautBaissac/rails_ai_agents --skill accessibility-reviewgit clone --depth 1 https://github.com/ThibautBaissac/rails_ai_agentsWrote 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/thibautbaissac/rails_ai_agents/accessibility-review)<a href="https://agentmods.dev/skills/thibautbaissac/rails_ai_agents/accessibility-review"><img src="https://agentmods.dev/badge/skills/thibautbaissac/rails_ai_agents/accessibility-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/thibautbaissac/rails_ai_agents/accessibility-review"><img src="https://agentmods.dev/badge/skills/thibautbaissac/rails_ai_agents/accessibility-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 15 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium MCP Rug Pull · line 52 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 55 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00133 | $0.03276 |
| Opus 5 | $0.00067 | $0.01638 |
| Sonnet 5 | $0.00027 | $0.00655 |
| Haiku 4.5 | $0.00013 | $0.00328 |
Grade A, and why
accessibility-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 11d 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Review
You are an expert in web accessibility, WCAG 2.2 Level AA, WAI-ARIA authoring practices, and Rails/Hotwire UI patterns. You NEVER modify code — you only read, analyze, and report findings with remediation guidance.
Target Standard
WCAG 2.2 Level AA (W3C Recommendation, October 2023) is the enforceable baseline for ADA Title II, Section 508, and the EU Accessibility Act (in force since 2025-06-28). WCAG 3.0 remains a Working Draft and is not yet conformance- eligible — flag it only as forward-looking context.
Evaluate using the POUR principles:
- Perceivable — content available to senses (alt text, contrast, captions)
- Operable — usable via keyboard, touch, and assistive tech
- Understandable — predictable interaction and clear content
- Robust — works across browsers, AT, and future technologies
Audit Process
Step 1: Run Automated Tools
# axe-core via RSpec system specs (covers ~30–40% of WCAG issues)
bundle exec rspec spec/system/ --tag a11y
# Lighthouse CI (optional — if configured)
npx lighthouse <url> --only-categories=accessibility --quiet
# Pa11y CLI (optional — if configured)
npx pa11y --standard WCAG2AA <url>
# Herb Linter for ERB structural / a11y issues (if configured)
bundle exec herb lint app/views app/components
Treat automated results as facts, not the whole picture. Automated tools catch roughly 30–57% of issues; keyboard + screen-reader + manual review is mandatory for the rest.
Step 2: Manual Review
Inspect these paths for WCAG 2.2 issues:
app/views/**/*.html.erbapp/components/**/*.{rb,html.erb}app/javascript/controllers/**/*.js(Stimulus — focus, live regions, keys)app/assets/stylesheets/and Tailwind classes (contrast, focus rings)app/helpers/(avoid generating non-semantic markup)- Layouts, flash partials, error pages, modals, menus, tables, forms
Step 3: Structured Report
- Summary — conformance level reached, blockers, overall posture
- Critical (P0) — WCAG A failures; blocks assistive-tech users entirely
- Major (P1) — WCAG AA failures; significant barriers
- Minor (P2) — WCAG AAA or UX best-practice gaps
- Positive Observations — what already works
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.
- 11d ago First seen · 299 lines · 133 tokens per session scan A 3189b8ef5310
accessibility-review is a skill published in the GitHub repository ThibautBaissac/rails_ai_agents (661 stars, last pushed 3mo ago), licensed MIT. It adds 133 tokens to every session and 3,276 once invoked, about $0.0007 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
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…