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/eliornl/rolemuleWrote 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/eliornl/rolemule/accessibility)<a href="https://agentmods.dev/rules/eliornl/rolemule/accessibility"><img src="https://agentmods.dev/badge/rules/eliornl/rolemule/accessibility/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/eliornl/rolemule/accessibility"><img src="https://agentmods.dev/badge/rules/eliornl/rolemule/accessibility.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.00452 |
| Opus 5.5 | $0.00000 | $0.00181 |
| Sonnet 5.5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
accessibility 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.
What it actually says
Accessibility (WCAG 2.1 AA)
Target: 100% Lighthouse accessibility score. Run npx lighthouse http://localhost:8000/ --only-categories=accessibility to verify.
Heading Hierarchy — Never Skip Levels
<!-- ✅ Correct -->
<h1>Page Title</h1>
<h2>Section</h2>
<h3>Subsection</h3>
<!-- ❌ Wrong — skips h2 -->
<h1>Page Title</h1>
<h3>Section</h3>
Use CSS classes to change visual size without changing semantic level: <h2 class="h4">.
Page Landmarks — Required on Every Page
<body>
<nav>...</nav>
<main><!-- all primary content --></main>
<footer>...</footer>
</body>
<main> must NOT include <nav> or <footer>.
Buttons and Interactive Elements
<!-- ✅ Icon-only button — must have aria-label -->
<button aria-label="Delete application" data-action="delete" data-id="...">
<i class="fas fa-trash"></i>
</button>
<!-- ❌ Wrong — no accessible name -->
<button><i class="fas fa-trash"></i></button>
- All
<input>/<select>/<textarea>must have associated<label for="...">oraria-label - Links must have descriptive text, not just "click here"
Images and Icons
- Decorative:
<img alt="">(empty string, not missing) - Informative: descriptive
alttext - Icon fonts (Font Awesome): decorative unless they are the only content of a button
Color and Contrast
- Normal text: minimum 4.5:1 contrast ratio
- Large text (18px+ or 14px+ bold): minimum 3:1
- Never use color as the sole means to convey information (add icons or text labels)
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 · 56 lines · 0 tokens per session scan A 95bf2ed8508f
accessibility is a cursor rule published in the GitHub repository eliornl/rolemule (38 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 452 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-30.
Other cursor rules, from other repositories
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.