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/rules/vanessamarely/ai-playbook-reposito/a11y-automation)<a href="https://agentmods.dev/rules/vanessamarely/ai-playbook-reposito/a11y-automation"><img src="https://agentmods.dev/badge/rules/vanessamarely/ai-playbook-reposito/a11y-automation/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/rules/vanessamarely/ai-playbook-reposito/a11y-automation"><img src="https://agentmods.dev/badge/rules/vanessamarely/ai-playbook-reposito/a11y-automation.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.01001 |
| Opus 5.5 | $0.00000 | $0.00400 |
| Sonnet 5.5 | $0.00000 | $0.00200 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
a11y-automation 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 2mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Automation
Run automated accessibility checks using linters and browser-based testing tools to identify WCAG violations. Not for manual component review, building new components (see react-components), or non-React/non-browser environments.
For a full guided audit with remediation, run /a11y-audit-react.
Procedure
- Validate the target path — for lint checks, look for
.tsx/.jsx/.ts/.jsfiles; for browser checks, look for test files or a running application. - Run linting checks: verify
eslint-plugin-jsx-a11yis configured, run eslint on the target path, group violations by rule. If not configured, output setup instructions (npm install --save-dev eslint-plugin-jsx-a11yand add it to the eslint config'splugins/extends). - Run browser-based checks (optional): if Playwright and
@axe-core/playwrightare available, run axe checks against rendered components or pages and report violations by severity. If not configured, provide install guidance (npm install --save-dev @playwright/test @axe-core/playwright). - Parse results: total violation count, violations by severity (critical, serious, moderate, minor), violations grouped by rule, file and line number for each.
- Summarize findings in chat: summary statistics, per-file breakdown with line numbers, brief description of each violation type.
- Propose fixes for critical/serious violations: show the offending snippet, the corrected version, the applicable WCAG guideline, and apply the fix as a minimal diff.
- Suggest CI integration if checks aren't already wired in: npm script examples, pre-commit hook setup, automated PR checks.
Error Handling
- Linter not configured: output install/config steps for
eslint-plugin-jsx-a11y. - Playwright not available: output install steps for Playwright +
@axe-core/playwright. - No violations found: report success and confirm checks ran.
- Critical violations found: treat as a failing check for CI/CD purposes (non-zero exit code).
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.
- 2mo ago First seen · 60 lines · 0 tokens per session scan A d1d184f1b96c
a11y-automation is a cursor rule published in the GitHub repository vanessamarely/ai-playbook-reposito (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,001 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 cursor rules, from other repositories
test
React best practices and patterns for modern web applications globs: /\.tsx, /.jsx, test/\\/.
e2e-playwright
Playwright e2e for App Builder — scenarios, snapshots, deploy skip, and when to add entries.
puppeteer
This guide provides opinionated, actionable best practices for writing robust, performant, and maintainable Puppeteer scripts for web scraping, automation, and testing. It emphasizes modern patterns like page.locator() and efficient resource management.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.