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/abderrahimghazali/cursor-rules/accessibility-standardsgit clone --depth 1 https://github.com/abderrahimghazali/cursor-rulesWhat 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.00000 | $0.00658 |
| Opus 5 | $0.00000 | $0.00329 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
accessibility-standards 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 2d 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.
This is a copy
89% identical to accessibility-standards — 71 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Accessibility Standards
Ensures WCAG compliance and accessibility best practices.
actions:
-
type: enforce conditions:
-
pattern: "<img[^>]+(?!alt=)[^>]*>" message: "Images must have alt attributes for screen readers."
-
pattern: "aria-[a-z]+=""" message: "ARIA attributes should not be empty; provide meaningful values."
-
pattern: "<button[^>]>(?![^<][^\s])[^<]*" message: "Buttons should have meaningful, descriptive content."
-
pattern: "<a[^>]href="#[^"]"[^>]>(?![^<]<svg)[^<]*" message: "Links with href='#' should either be removed or have an aria-label for context."
-
pattern: "<input[^>]+type="(text|email|password|search|tel|url)"[^>]*>" pattern_negate: "aria-label|aria-labelledby|title" message: "Form inputs should include an aria-label or aria-labelledby attribute for better screen reader support."
-
pattern: "<video[^>]>(?!<track)[^<]" message: "Videos should include captions for accessibility."
-
-
type: suggest message: | Accessibility Best Practices:
- Heading Hierarchy: Use headings (h1 to h6) in a logical order to structure content.
- Keyboard Navigation: Ensure all interactive elements are accessible via keyboard.
- Semantic HTML: Favor semantic elements like , , , and for better structure comprehension.
- Color Contrast: Check color contrast ratios meet WCAG guidelines (4.5:1 for normal text, 7:1 for large text).
- Skip Navigation Links: Provide 'skip to main content' links for keyboard users to bypass repetitive navigation.
- Focus Management: Ensure focus indicators are visible and manage focus for modal dialogs or dynamic content changes.
- Form Labels: Associate labels with form controls using the 'for' attribute or wrap controls with .
- Descriptive Links: Use descriptive text for links, avoiding generic phrases like "click here."
- Touch Targets: Ensure touch target sizes are large enough (at least 44x44 pixels) for mobile users.
- Timeouts: Avoid or provide options to extend time limits where possible, or warn users before session expiry.
- Language Attribute: Set the lang attribute on the element to indicate the primary language of the page.
metadata: priority: high version: 1.1
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.
- 2d ago First seen · 56 lines · 658 tokens per session scan A 8d26a40a6b00
accessibility-standards is a cursor rule published in the GitHub repository abderrahimghazali/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 658 tokens. A static security scan graded it A with 0 findings. It is 89% identical to accessibility-standards, differing in 71 lines, and is treated as a copy.
Other cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
cursorrules
You are a disciplined senior engineer working with someone who may be a domain expert, not a programmer. Build it correctly and safely, not just fast.
cursorrules
Cursor rule "cursorrules" from BlueBirdBack/godot-cursorrules, covering godot 4.4 game development .cursorrules, core development guidelines, code style, naming conventions and scene organization.
new_feature
You are an expert Product Owner and Technical Lead focused on helping users define and plan new features through collaborative discovery and structured documentation.
new_project
You are an expert Product Owner focused on helping users define new software projects through collaborative vision creation.