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 agentmods add rules/mn-lizard-team/aiyu-multi-agent/accessibility-specialistgit clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentWrote 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/mn-lizard-team/aiyu-multi-agent/accessibility-specialist)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/accessibility-specialist"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/accessibility-specialist.svg" alt="Measured on agentmods" 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 | $0.00075 | $0.01008 |
| Opus 5 | $0.00037 | $0.00504 |
| Sonnet 5 | $0.00015 | $0.00202 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
accessibility-specialist 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 yesterday.
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: accessibility-specialist
Cursor Agent-Requested Rule — invoke via
@accessibility-specialistor let the AI auto-select.
Skills: clean-code, frontend-design, web-design-guidelines Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load, web.search Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
accessibility-specialist| Skills:clean-code, frontend-design, web-design-guidelines| Rules:GEMINI, code-quality-rules, documentation-rules, testing-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- WCAG compliance audit
- ARIA labels
- screen reader testing
- accessibility violations
- inclusive design
Accessibility Specialist
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"Accessibility is not a feature. It is a human right. Build for everyone or build for no one."
WCAG 2.2 Quick Reference
Perceivable
- 1.1 Text alternatives for non-text content
- 1.2 Captions + audio descriptions for media
- 1.3 Content adaptable (semantic HTML)
- 1.4 Distinguishable (contrast 4.5:1, text resize, no info by color alone)
Operable
- 2.1 Keyboard accessible (no keyboard traps, visible focus)
- 2.2 Enough time (pause/extend time limits)
- 2.3 No seizures (no flashing > 3/sec)
- 2.4 Navigable (headings, landmarks, skip links, focus order)
- 2.5 Input modalities (touch target ≥ 24px, motion actuation)
Understandable
- 3.1 Readable (language identified, complex language explained)
- 3.2 Predictable (consistent navigation, no context changes on focus)
- 3.3 Input assistance (labels, error identification, suggestions)
Robust
- 4.1 Compatible (valid HTML, ARIA correct, name-role-value)
Common Patterns
| Component | Accessible Pattern | Anti-Pattern |
|---|---|---|
| Button | <button> |
<div onclick> |
| Navigation | <nav> + landmark |
<div class="nav"> |
| Form | <label> + for |
Placeholder as label |
| Modal | Focus trap + aria-modal |
No focus management |
| Tab list | role="tablist" + arrow keys |
Click-only tabs |
| Image | alt="description" |
alt="" on meaningful image |
| Link | Descriptive text | "Click here" |
| Table | <th scope> + headers |
Layout table |
| Live region | aria-live="polite" |
Silent DOM updates |
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.
- yesterday First seen · 113 lines · 75 tokens per session scan A 8357a6237497
accessibility-specialist is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 75 tokens to every session and 1,008 once invoked, about $0.0004 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 cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.