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/abderrahimghazali/cursor-rulesWrote 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/abderrahimghazali/cursor-rules/accessibility-standards)<a href="https://agentmods.dev/rules/abderrahimghazali/cursor-rules/accessibility-standards"><img src="https://agentmods.dev/badge/rules/abderrahimghazali/cursor-rules/accessibility-standards/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/abderrahimghazali/cursor-rules/accessibility-standards"><img src="https://agentmods.dev/badge/rules/abderrahimghazali/cursor-rules/accessibility-standards.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.00658 |
| Opus 5.5 | $0.00000 | $0.00263 |
| Sonnet 5.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 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.
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.
- 1mo 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
react-chakra-ui-cursorrules-prompt-file
Cursor rules for React development with Chakra UI integration.
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.
react-chakra-ui---folder-structure
A standard folder layout for React and Chakra UI projects, including separate locations for components, pages, themes, hooks, utilities, and assets. It also defines how Chakra UI theme files are grouped.
uizze-ui-finish-gate
Apply the UIZZE design contract and finish gate to frontend work.
best_practices
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.