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 The-AI-Directory-Company/agents-and-skills --skill accessibility-audit-reportgit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-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/the-ai-directory-company/agents-and-skills/accessibility-audit-report)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/accessibility-audit-report"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/accessibility-audit-report/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/the-ai-directory-company/agents-and-skills/accessibility-audit-report"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/accessibility-audit-report.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.00034 | $0.01572 |
| Opus 5 | $0.00017 | $0.00786 |
| Sonnet 5 | $0.00007 | $0.00314 |
| Haiku 4.5 | $0.00003 | $0.00157 |
Grade A, and why
accessibility-audit-report 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 8d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Audit Report
Before you start
Gather the following from the user. If anything is missing, ask before proceeding:
- Scope — Which pages, flows, or components are being audited? (e.g., "checkout flow", "marketing site", "design system")
- Target conformance level — WCAG 2.1 AA (most common), WCAG 2.2 AA, or AAA?
- Testing methods used — Automated tools (axe, Lighthouse), manual keyboard/screen reader testing, user testing with disabled participants?
- Tech stack — Framework, component library, and any existing a11y tooling in the pipeline
- Audience context — Is there a legal compliance deadline, a known user complaint, or a proactive audit?
If the user says "just audit everything," push back: "Which user flows are highest traffic or highest risk? Start there — a focused audit produces actionable results, a broad audit produces a backlog nobody reads."
Audit report template
1. Executive Summary
3-5 sentences. State the overall conformance status, the number of issues found by severity, and the single most critical finding. This section is for stakeholders who will not read the full report.
This audit evaluated 12 screens across the checkout flow against WCAG 2.1 AA.
We identified 23 issues: 4 critical, 7 major, 9 minor, and 3 best-practice
recommendations. The most critical finding is that the payment form is entirely
inaccessible to keyboard-only users, blocking approximately 8% of users from
completing purchases.
2. Scope & Methodology
List what was tested, what was not, and how. Be explicit about tools and versions.
Tested: /cart, /checkout/shipping, /checkout/payment, /checkout/confirmation
Not tested: Account settings, admin dashboard
Methods: axe-core 4.9, NVDA 2024.1 + Chrome, VoiceOver + Safari, manual
keyboard navigation, color contrast analyzer
3. Summary of Findings
Provide a scannable table. Every issue in the report must appear here.
| # | Issue | WCAG Criterion | Severity | Component/Page |
|---|---|---|---|---|
| 1 | Payment form not keyboard accessible | 2.1.1 Keyboard | Critical | /checkout/payment |
| 2 | Images missing alt text | 1.1.1 Non-text Content | Major | /cart |
| 3 | Insufficient color contrast on helper text | 1.4.3 Contrast (Minimum) | Minor | Global |
What ships with it
4 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.
- 8d ago First seen · 133 lines · 34 tokens per session scan A 999765d007f4
accessibility-audit-report is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,572 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
ss-review
Review UI code for design system compliance, accessibility, and best practices.
brand-identity
Brand strategy and identity design for businesses and products. Use when creating brand guidelines, developing visual identity systems, or defining brand positioning.
ai-policy-generator
AI governance policy creation for nonprofits and enterprises with frameworks, risk assessment, ethical guidelines, and compliance templates. Use when drafting AI usage policies, responsible AI frameworks, or organizational AI governance documents.
graphic-design
Professional graphic design principles for digital and print media. Use when creating visual designs, choosing color palettes, typography, layouts, or providing design feedback.
generic-react-ux-designer
Professional UI/UX design expertise for React applications. Covers design thinking, user psychology (Hick's/Fitts's/Jakob's Law), visual hierarchy, interaction patterns, accessibility, performance-driven design, and design critique. Use when designing features, improving UX, solving user problems, or conducting design…
generic-design-system
Complete design system reference for any project - colors, typography, spacing, components, animations. Adapts to project theme and tech stack. Use when implementing UI, choosing colors, creating animations, or ensuring brand consistency. For new design systems, use ui-research skill first.