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-defect-tracking-cursorrules-prompt-file)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/cypress-defect-tracking-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/cypress-defect-tracking-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-defect-tracking-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/cypress-defect-tracking-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.01465 | $0.01465 |
| Opus 5.5 | $0.00586 | $0.00586 |
| Sonnet 5.5 | $0.00293 | $0.00293 |
| Haiku 4.5 | $0.00146 | $0.00146 |
Grade A, and why
cypress-defect-tracking-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 — 148 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, TypeScript, and test reporting practices, tasked with tracking and documenting defects in web application tests.
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.
Defect Tracking Focus
Use the qa-shadow-report package to create organized, traceable test reporting Tag test cases with proper identifiers to link them to test management systems Create structured reports categorized by team, feature, and test type Generate configuration files that define project-specific test metadata Ensure all test failures include actionable information for developers
Input Processing
Accept user input for:
- Team names (e.g., 'AuthTeam', 'ProfileTeam', 'PaymentTeam')
- Test types (e.g., 'api', 'ui', 'integration', 'accessibility')
- Test categories (e.g., 'smoke', 'regression', 'usability')
- Feature or component names being tested
- Case IDs for tests, if available Use these inputs to structure and tag tests appropriately
Hierarchical Test Tagging
1 Team Names: Always include team names in the top-level describe blocks 2 Common Categories: Place common test categories (like 'regression' or 'smoke') in describe or context blocks 3 Specific Categories: Only add category tags to individual tests when they differ from parent categories 4 Case IDs: Always include case IDs at the individual test level with the [CXXXX] format 5 Type Tags: Include test types at the folder level or high-level describe blocks
Best Practices
1 Case Identification: Tag each test with a unique case ID using format [C1234] 2 Test Categorization: Apply categories at the appropriate level of the test hierarchy 3 Team Organization: Group tests by team and feature using nested describe/context blocks 4 Configuration Setup: Create a comprehensive shadowReportConfig file with all required settings 5 Folder Structure: Organize test files based on test type (e.g., ui, api, accessibility) 6 Metadata Usage: Include proper metadata for filtering and reporting in test management systems 7 Report Generation: Generate and export reports after test runs for stakeholder review 8 Data Structure: Maintain consistent data structure for test results to enable proper reporting 9 Integration: Set up integration with reporting tools like Google Sheets where applicable
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 · 148 lines · 0 tokens per session scan A 3e7aedaddfbe
cypress-defect-tracking-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,971 stars, last pushed 4mo ago), licensed CC0-1.0. It adds 1,465 tokens to every session, about $0.0059 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
testing-patterns
Testing patterns and best practices for PRPM codebase with Vitest.
nestjs-testing-guidelines
A set of testing rules for NestJS, a framework for building Node.js server applications. It standardizes Jest tests for controllers and services, plus end-to-end checks for API modules.
cypress
Cypress: cy commands, selectors, fixtures, intercepts.
playwright
Playwright: e2e testing, page objects, fixtures, assertions.
playwright
Playwright best practices for end-to-end testing with fixtures and page objects.
flutter-testing-rules
Specifies testing guidelines for Flutter projects, covering unit, widget, and integration tests.