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.
git clone --depth 1 https://github.com/vanessamarely/ai-playbook-repositoWrote 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/commands/vanessamarely/ai-playbook-reposito/a11y-audit-react)<a href="https://agentmods.dev/commands/vanessamarely/ai-playbook-reposito/a11y-audit-react"><img src="https://agentmods.dev/badge/commands/vanessamarely/ai-playbook-reposito/a11y-audit-react/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/commands/vanessamarely/ai-playbook-reposito/a11y-audit-react"><img src="https://agentmods.dev/badge/commands/vanessamarely/ai-playbook-reposito/a11y-audit-react.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.00000 | $0.00936 |
| Opus 5 | $0.00000 | $0.00468 |
| Sonnet 5 | $0.00000 | $0.00187 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
a11y-audit-react 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 10d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Audit (React)
Identify accessibility violations in React components and provide actionable remediation aligned with WCAG 2.2 Level AA. This is the guided audit workflow that applies the standards defined in the a11y-automation and react-components rules.
Inputs
targetPath: path to component file(s) or directory to audit.auditScope:single-file,directory, orfull-project.
Outputs
- Summary of violations by severity (critical, serious, moderate, minor).
- Actionable code fixes with minimal diffs.
- Verification commands to confirm the fixes.
Procedure
- Validate scope — confirm
targetPathexists, determine files to audit perauditScope, filter to.tsx/.jsx. - Run automated lint — execute the project's
eslint-plugin-jsx-a11ychecks overtargetPathand capture violations (see thea11y-automationrule for setup guidance if it's not configured). - Analyze each component manually:
- Semantic HTML: flag
<div>/<span>used for buttons/links; flag missing landmarks (<header>,<nav>,<main>,<footer>). - Keyboard navigation: verify interactive elements have both
onClickandonKeyDown; check for keyboard traps in modals/focus-managed sections. - ARIA usage: flag missing
aria-label/aria-labelledbyon icon buttons, invalid ARIA combinations, redundant ARIA on already-semantic elements. - Focus management: verify modals trap and restore focus; verify dynamic content announces via
aria-livewhere needed. - Contrast and motion: flag hardcoded colors that may violate contrast ratios; flag animations without
prefers-reduced-motionhandling.
- Semantic HTML: flag
- Categorize violations:
- Critical: component unusable via keyboard or screen reader.
- Serious: missing required ARIA or semantic structure.
- Moderate: suboptimal patterns that hinder usability.
- Minor: best-practice improvements.
- Summarize findings in chat — total counts, per-file breakdown with line numbers, brief description per violation.
- Propose fixes — for each violation, show the problematic snippet, the corrected version, and the accessibility benefit; apply as minimal diffs.
- Suggest automated regression tests — if Playwright/axe-core is available in the project, suggest wiring the checks into the test suite (see
a11y-automation).
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.
- 10d ago First seen · 61 lines · 0 tokens per session scan A c1856476a78c
a11y-audit-react is a command published in the GitHub repository vanessamarely/ai-playbook-reposito (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 936 tokens. 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 commands, from other repositories
prototype-loop
Enter leveraged-prototype focus mode — focus marker plus normal watch/rebuild loop for visual-parity work and batch upstream framework gap-fixes.
review-arch
Review the current branch for code quality, TypeScript, and React/Next.js patterns. Supports whole-branch review or scoped review by path, feature, or base branch.
create-variant
Add a new variant to an existing shadcn/ui component.
react-build
Fix React build failures (Vite, webpack, Next.js, CRA, Parcel, esbuild, Bun) incrementally — JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types. Invokes the react-build-resolver agent for minimal, surgical fixes.
next-upgrade
Structured workflow for upgrading Next.js applications across major versions. Use when migrating a Next.js project from one major version to another (e.g., 13 to 14, 14 to 15, 15 to 16). Covers codemod automation, breaking change detection, incremental migration paths, and post-upgrade validation.
web-design
Design and build a complete website or webapp from a project brief — end-to-end workflow from design to working React/Vite code.