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 d-o-hub/github-template-ai-agents --skill accessibility-auditorgit clone --depth 1 https://github.com/d-o-hub/github-template-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/d-o-hub/github-template-ai-agents/accessibility-auditor)<a href="https://agentmods.dev/skills/d-o-hub/github-template-ai-agents/accessibility-auditor"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/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/d-o-hub/github-template-ai-agents/accessibility-auditor"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/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.00100 | $0.00696 |
| Opus 5.5 | $0.00040 | $0.00278 |
| Sonnet 5.5 | $0.00020 | $0.00139 |
| Haiku 4.5 | $0.00010 | $0.00070 |
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 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Auditor
Audit web applications for WCAG 2.2 compliance, screen reader compatibility, keyboard navigation, and color contrast issues.
When to Use
- User asks for an accessibility audit or a11y check
- Reviewing WCAG 2.2 compliance or Section 508/ADA requirements
- Testing screen reader compatibility or keyboard navigation
- Checking color contrast or ARIA validation
- Even if they just say "is this accessible" or "check for accessibility issues"
Audit Workflow
Phase 1: Automated Scan
Check these automatically using axe-core, Lighthouse, or WAVE:
- Color contrast (1.4.3)
- Missing alt text (1.1.1)
- Form labels (3.3.2)
- Heading hierarchy (1.3.1)
Phase 2: Manual Testing
- Screen Reader: Navigate with NVDA/VoiceOver/JAWS arrow keys.
- Keyboard: Verify Tab order and focus indicators (2.4.7).
- Zoom: Test reflow at 400% zoom (1.4.10).
Severity Classification
| Severity | Impact | Priority |
|---|---|---|
| Critical | Blocks access | Fix immediately |
| High | Significant barrier | Fix before release |
| Medium | Minor friction | Next sprint |
| Low | Enhancement | Backlog |
See Also
css-render-performance— CSS render performance optimizationui-ux-optimize— UI/UX optimization with swarm agents
Rationalizations
| Rationalization | Reality |
|---|---|
| "Automated scans catch everything" | Automated tools miss keyboard traps, focus order, screen reader semantics, and cognitive load issues. |
| "Accessibility only matters for blind users" | Motor, cognitive, and situational impairments affect far more users than visual alone. |
| "We'll fix accessibility in the next release" | Each release without a11y compounds legal risk and excludes users; fix forward. |
Red Flags
- Only automated scans run without manual keyboard/screen reader testing
- Color contrast issues deferred as cosmetic
- ARIA labels applied without role verification
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.
- 1mo ago First seen · 76 lines · 100 tokens per session scan A 0260a7cb3020
accessibility-auditor is a skill published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 696 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
ui-ux-pro-max-skill
UI UX Pro Max is one skill, not a collection, that produces a design system from a description of a project. Its README states it draws on a library of 79 UI styles, 192 color palettes, and 74 font pairings, outputting pattern, color, typography, and effects choices along with an anti-pattern checklist.
accessibility-ui-design
When designing and implementing web interfaces to ensure they are usable by everyone.
premium-saas-design
The Define, Build, Review, Refine loop and seven context artifacts (brief, content, mood boards, section specs, style guide, PRD, tasks) for building a premium SaaS marketing site with AI. Use when planning or building a SaaS landing page and you want the design context written down before any code.
design-movements
Design movements from Arts and Crafts through Bauhaus, Swiss Style, Memphis, and grunge to flat design and current styles, with context, visual markers, and UI tokens for each. Use when choosing an aesthetic direction, explaining why a style reads the way it does, or applying a period style without misusing it.
brand-systems
Brand identity building blocks: positioning, personality, archetypes, logo systems, color palettes, type pairing, voice, and guidelines documentation. Use when creating a brand, rebranding, or turning an existing identity into tokens and rules others can follow.
design-masters
Working profiles of Saul Bass, Massimo Vignelli, Dieter Rams, Paula Scher, Josef Müller-Brockmann, David Carson, and Paul Rand: key works, principles, and how to apply each in UI work. Use when a design needs a proven approach, a named reference to follow, or a lesson from a specific master.