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 codebygarv/Ai-skills --skill accessibility-auditorgit clone --depth 1 https://github.com/codebygarv/Ai-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/codebygarv/ai-skills/accessibility-auditor)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/accessibility-auditor"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/accessibility-auditor/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/codebygarv/ai-skills/accessibility-auditor"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/accessibility-auditor.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.00042 | $0.00622 |
| Opus 5 | $0.00021 | $0.00311 |
| Sonnet 5 | $0.00008 | $0.00124 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
accessibility-auditor 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 5d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Audit a UI implementation against core accessibility principles so it's usable by people relying on keyboard navigation, screen readers, or other assistive technology — not just usable with a mouse and full vision.
When to Use
- Before shipping any user-facing UI, especially public-facing products.
- Reviewing a form, modal, or interactive component specifically.
- The user asks for an accessibility review/audit, or mentions WCAG/a11y compliance requirements.
What to Analyze
- Semantic HTML — using actual
<button>,<a>,<nav>,<form>, heading levels (<h1>–<h6>) instead of generic<div>/<span>with click handlers or visual-only styling standing in for structure. - Keyboard navigation — every interactive element reachable and operable via keyboard alone (Tab, Enter/Space, Escape for dismissible elements), with a visible focus indicator.
- Labels & names — form inputs with associated
<label>s (oraria-label), buttons/icons with accessible names (not just an icon with no text alternative), images with meaningfulalttext (or emptyalt=""if purely decorative). - Color contrast — text-to-background contrast meeting at least WCAG AA (4.5:1 for normal text, 3:1 for large text), and that meaning isn't conveyed by color alone (e.g. error state needs more than just red text).
- Screen reader behavior — dynamic content changes (loading states, form errors, toasts) announced via appropriate ARIA live regions; modal/dialog focus trapping and return-focus-on-close behavior.
- ARIA usage correctness — flag ARIA attributes used incorrectly or redundantly (ARIA on top of already-semantic HTML, or roles that don't match actual behavior) — "no ARIA is better than bad ARIA."
Output Format
- Findings grouped by WCAG-adjacent category (Semantics, Keyboard, Labels, Contrast, Screen Reader, ARIA).
- Each finding: the specific element/pattern, the concrete barrier it creates (what a keyboard/screen-reader user actually can't do), and the fix.
- Note severity: Blocker (a user with a disability literally cannot complete the task) vs. Improvement (usable but suboptimal).
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.
- 5d ago First seen · 36 lines · 42 tokens per session scan A fe094f2752b2
accessibility-auditor is a skill published in the GitHub repository codebygarv/Ai-skills (25 stars, last pushed 19d ago), licensed MIT. It adds 42 tokens to every session and 622 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
bun-api
Bun runtime API reference for TypeScript scripts. Covers Bun.serve() HTTP/HTTP/2 server with routes and WebSockets, fetch() transport options, Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite, Bun.sql() for PostgreSQL/MySQL via DATABASEURL, Bun.s3 for S3-compatible storage, Bun.redis…
bun-cli
Bun CLI reference for package management, script running, testing, bundling, and compilation. Covers bun install/add/remove/update, bun run, bun test, bun build, bunx, bun patch, bun audit fix, bun dedupe, bun prune, bun why, bun pm, bun repl, bunfig.toml, bun.lock, workspace catalogs, isolated installs and the global…
deps-upgrade
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates.…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…