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 arcasilesgroup/ai-engineering --skill a11y-auditgit clone --depth 1 https://github.com/arcasilesgroup/ai-engineeringWrote 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/arcasilesgroup/ai-engineering/a11y-audit)<a href="https://agentmods.dev/skills/arcasilesgroup/ai-engineering/a11y-audit"><img src="https://agentmods.dev/badge/skills/arcasilesgroup/ai-engineering/a11y-audit/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/arcasilesgroup/ai-engineering/a11y-audit"><img src="https://agentmods.dev/badge/skills/arcasilesgroup/ai-engineering/a11y-audit.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.00080 | $0.02072 |
| Opus 5.5 | $0.00032 | $0.00829 |
| Sonnet 5.5 | $0.00016 | $0.00414 |
| Haiku 4.5 | $0.00008 | $0.00207 |
Grade A, and why
a11y-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 1mo 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility audit
Find the places where someone cannot use this app. Every finding names the user and the barrier: "a keyboard user cannot dismiss this dialog" is a finding; "missing ARIA attributes" is a lint message.
Read .claude/review/CONVENTIONS.md first — stack detection, scope, severity,
false-positive gate, report format. Target is WCAG 2.2 level AA.
WCAG is an external standard, so this skill is largely stack-independent — but where the checks below name a file or a styling mechanism, map it to whatever this project actually uses. Identify these three things up front:
- The root document shell — wherever
<html lang>, landmarks, and the page skeleton are set (a root layout, a template,index.html, a base view). - The global stylesheet and design tokens — wherever focus resets, color variables, and motion settings live.
- The styling mechanism — utility classes, CSS modules, CSS-in-JS, or plain stylesheets. This decides how you resolve a color to an actual value in §6.
Checklist
1. Semantics before ARIA
The most common real defect is a <div> doing a control's job. A <div onClick> is invisible to screen readers, not focusable, and does not fire on
Enter/Space — use <button>. Likewise: <a> for navigation, <button> for
actions (an <a> with no href is not focusable), real <ul>/<li> for lists,
<table> with <th scope> for tabular data.
Check landmarks (main, nav, header, footer) exist and are not duplicated
without labels; exactly one <h1> per page; heading levels that descend without
skipping; <html lang> set in the root document shell.
The first rule of ARIA is not to use ARIA. A native element with correct
semantics beats role="button" plus three attributes. Report added ARIA as a
finding when a native element would have worked.
2. Keyboard operability Walk each interactive element and ask: can I reach it with Tab, operate it with Enter/Space, and leave it?
- Anything interactive must be reachable.
tabIndex={-1}on a control, or a custom widget with notabIndex, removes it. - Focus traps — modals/menus that keep focus inside with no Escape route. Critical severity: the user is stuck.
- Positive
tabIndex(tabIndex={1}+) breaks document order. Always a finding. - Tab order must follow visual order — watch for CSS (
order,flex-direction: row-reverse, absolute positioning) that reorders visually but not in the DOM. - Custom widgets need their expected key handling (Escape closes, arrows move within a composite control).
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.
- 1mo ago First seen · 166 lines · 80 tokens per session scan A 8e6909c4399d
a11y-audit is a skill published in the GitHub repository arcasilesgroup/ai-engineering (61 stars, last pushed 2d ago), licensed Apache-2.0. It adds 80 tokens to every session and 2,072 once invoked, about $0.0003 per session on Opus 5.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-09-12.
Other skills, from other repositories
review
WCAG 2.2 AA curated accessibility review — distinguishes automatically detectable, browser-assisted, and manual/human-judgment findings with evidence citations and SC mapping. Composes with design-assessment/design-improvement/frontend-design-review.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
ui-ux-design
Create production-grade frontend interfaces with strong UX and visual craft. Use when building web components, pages, dashboards, forms, landing pages, modals, or any UI. Use when user says 'build a form', 'create a dashboard', 'design a component', 'make a landing page', or asks for UI/UX work. Use even when the user…
frontend-design-review
Review and create distinctive, production-grade frontend interfaces with high design quality and design system compliance. Evaluates using three pillars: frictionless insight-to-action, quality craft, and trustworthy building. USE FOR: PR reviews, design reviews, accessibility audits, design system compliance checks…
visual-artifact-qa
Visual output that passes static checks can still fail to render.
frontend-design
Use this skill when building UI components, designing frontend architecture, implementing styling systems, optimizing performance, ensuring accessibility, or creating production-grade interfaces. Trigger on keywords: frontend, component, UI, styling, React, Next.js, Angular, Tailwind, CSS, responsive, accessibility…