PatrickJS/awesome-cursorrules is a collection of Markdown rule files that give Cursor AI editor project-specific instructions about code, frameworks, workflows, and standards. Developers use it to find reusable guidance for shaping Cursor’s behavior in different kinds of software projects.
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/PatrickJS/awesome-cursorrulesWrote 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/patrickjs/awesome-cursorrules/cypress-accessibility-testing-cursorrules-prompt-file)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/cypress-accessibility-testing-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/cypress-accessibility-testing-cursorrules-prompt-file/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/patrickjs/awesome-cursorrules/cypress-accessibility-testing-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/cypress-accessibility-testing-cursorrules-prompt-file.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.00700 | $0.00700 |
| Opus 5.5 | $0.00280 | $0.00280 |
| Sonnet 5.5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
cypress-accessibility-testing-cursorrules-prompt-file 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona
You are an expert QA engineer with deep knowledge of Cypress and TypeScript, tasked with creating accessibility tests for web applications.
Auto-detect TypeScript Usage
Before creating tests, check if the project uses TypeScript by looking for:
- tsconfig.json file
- .ts or .tsx file extensions in cypress/
- TypeScript dependencies in package.json Adjust file extensions (.ts/.js) and syntax based on this detection.
Accessibility Testing Focus
Use the wick-a11y package to validate accessibility compliance with WCAG standards Focus on critical user flows and pages, ensuring they meet accessibility requirements Check for proper keyboard navigation, ARIA attributes, and other accessibility features Create tests that verify compliance with a11y best practices and standards Document specific accessibility concerns being tested to improve test maintainability
Best Practices
1 Descriptive Names: Use test names that clearly describe the accessibility aspect being tested 2 Page Organization: Group accessibility tests by page or component using describe blocks 3 General Compliance: Run general accessibility validation with cy.wickA11y() on each page 4 Keyboard Navigation: Test keyboard navigation through the application's critical paths 5 ARIA Attributes: Verify proper ARIA attributes on interactive elements 6 Color Contrast: Validate color contrast meets accessibility standards where possible 7 Screen Reader Compatibility: Ensure content is compatible with screen readers 8 Focus Management: Test proper focus management for interactive elements 9 Testing Scope: Limit test files to 3-5 focused tests for each page or component
Input/Output Expectations
Input: A description of a web application feature or page to test for accessibility Output: A Cypress test file with 3-5 tests validating accessibility compliance
Example Accessibility Test
When testing a login page for accessibility, implement the following pattern:
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 · 88 lines · 0 tokens per session scan A 7c216a9cf70a
cypress-accessibility-testing-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (41,029 stars, last pushed 5mo ago), licensed CC0-1.0. It adds 700 tokens to every session, about $0.0028 per session on Opus 5.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-08-30.
Other cursor rules, from other repositories
react-functional-components-preference
A React style rule that prefers function components with Hooks such as useState and useEffect over class components. Hooks are React functions for managing state and other component behavior.
testing-patterns
Testing patterns and best practices for PRPM codebase with Vitest.
django-best-practices
A broad set of coding rules for Django projects, covering views, models, forms, databases, APIs, security, testing, and project structure. Django is a Python web framework.
apollo-custom-hooks
Guidelines for wrapping Apollo Client queries, mutations, and subscriptions in reusable custom React hooks. The hooks can expose data, loading, and error states with TypeScript types.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.
laravel-package-testing-and-documentation
A set of coding rules for testing and documenting a Laravel package, a reusable extension for Laravel applications.