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 commands/farzannajipour/cursor-react-rules/audit-accessibilitygit clone --depth 1 https://github.com/Farzannajipour/cursor-react-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/commands/farzannajipour/cursor-react-rules/audit-accessibility)<a href="https://agentmods.dev/commands/farzannajipour/cursor-react-rules/audit-accessibility"><img src="https://agentmods.dev/badge/commands/farzannajipour/cursor-react-rules/audit-accessibility.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.00000 | $0.01638 |
| Opus 5 | $0.00000 | $0.00819 |
| Sonnet 5 | $0.00000 | $0.00328 |
| Haiku 4.5 | $0.00000 | $0.00164 |
Grade A, and why
audit-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 3d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Accessibility
Overview
Comprehensive accessibility audit checklist for WCAG 2.1 AA compliance.
Steps
-
Semantic HTML
- Check proper heading hierarchy
- Verify semantic elements used
- Ensure landmarks are present
-
Keyboard Navigation
- Test tab order
- Verify all interactive elements accessible
- Check focus indicators visible
-
ARIA Attributes
- Add labels for screen readers
- Implement proper roles
- Use aria-live for dynamic content
-
Color & Contrast
- Verify color contrast ratios
- Don't rely on color alone
- Support dark mode
Accessibility Checklist
Semantic HTML
- Proper heading hierarchy (h1 → h2 → h3)
- Use
<button>for buttons (not<div>with onClick) - Use
<a>for links - Use
<nav>,<main>,<aside>,<article> - Form inputs have associated
<label> - Tables use
<th>,<caption>,scope
Keyboard Navigation
- All interactive elements accessible via Tab
- Logical tab order
- Skip to main content link
- Focus indicators visible
- Escape closes modals/dropdowns
- Arrow keys for lists/menus
- Enter/Space activate buttons
Screen Reader Support
- Images have alt text
- Decorative images have empty alt (
alt="") - Icon buttons have aria-label
- Form inputs have labels
- Error messages associated with inputs
- Loading states announced
- Dynamic content updates announced (aria-live)
ARIA Attributes
- aria-label for icon-only buttons
- aria-labelledby for complex labels
- aria-describedby for help text
- aria-invalid for errors
- aria-required for required fields
- aria-expanded for collapsibles
- role attributes where needed
Color & Contrast
- Text contrast ratio ≥ 4.5:1
- Large text contrast ≥ 3:1
- UI components contrast ≥ 3:1
- Focus indicators contrast ≥ 3:1
- Don't rely on color alone
- Links distinguishable from text
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.
- 3d ago First seen · 263 lines · 0 tokens per session scan A d0d56fa9c598
audit-accessibility is a command published in the GitHub repository Farzannajipour/cursor-react-rules (3 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,638 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.