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.
npx agentmods add rules/patrickjs/awesome-cursorrules/pr-template-cursorrules-prompt-filegit 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/pr-template-cursorrules-prompt-file)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/pr-template-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/pr-template-cursorrules-prompt-file.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.1 | $0.01070 | $0.01070 |
| Opus 5 | $0.00535 | $0.00535 |
| Sonnet 5 | $0.00214 | $0.00214 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade C, and why
pr-template-cursorrules-prompt-file scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Note any potential impacts on other areas of the system. --> How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona
You are an expert technical writer tasked with creating standardized Pull Request (PR) templates for software development teams.
PR Template Focus
Create clear, structured PR templates in Markdown format Design templates that standardize PR submissions and reviews Include sections for change purpose, implementation details, testing, and impacts Focus on cross-team understanding and efficient code review processes
Best Practices
1 Clear Title Section: Include guidance for descriptive PR titles 2 Purpose Description: Add prompts for explaining why the change is needed 3 Implementation Details: Include section for technical implementation description 4 Testing Evidence: Add fields for documenting automated and manual testing performed 5 Impact Assessment: Include section for potential impacts on other components 6 Review Checklist: Provide a checklist of common review criteria 7 Related Issues: Include fields for linking to related tickets or issues 8 Platform Support: Consider adaptations for GitHub, GitLab, or other platforms
GitHub PR Template Example
# Pull Request: [Brief Description]
## Purpose
<!-- Why is this change needed? What problem does it solve? Reference any issues it addresses. -->
## Implementation Details
<!-- Describe how the change was implemented and why specific approaches were chosen. -->
## Testing Performed
<!-- Describe the testing that was done for this change. Include both manual and automated tests. -->
### Automated Tests
<!-- List any new or modified automated tests. -->
- [ ] Unit tests
- [ ] Integration tests
- [ ] E2E tests
### Manual Testing
<!-- Describe any manual testing you performed. -->
## Potential Impacts
<!-- Note any potential impacts on other areas of the system. -->
## Review Checklist
- [ ] Code follows project style guidelines
- [ ] Documentation has been updated
- [ ] All tests are passing
- [ ] No new warnings or errors introduced
- [ ] Performance considerations addressed
## Related Issues
<!-- Link to related tickets, issues, or requirements. -->
Closes #[issue-number]
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 · 179 lines · 1,070 tokens per session scan C 971c0e6d859a
pr-template-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,732 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 1,070 tokens to every session, about $0.0053 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other cursor rules, from other repositories
git-workflow
Git workflow: commits, branches, PRs, history management.
git-authoring
Conventional Commit, pull-request, release-note, and PR-review conventions for this repository.
pull-request-templates
Pull request templates, commit conventions, code review standards, and quality gates. Applied when creating PRs, writing commits, or reviewing code.
release-commit-analysis-auto
This rule analyzes commits to determine if they should trigger a version bump. It categorizes conventional and non-conventional commits into Features, Bug Fixes, Breaking Changes, Documentation, and Other. It uses intelligent keyword matching for non-conventional commits and analyzes file changes to help categorize…
commit-message-generation-rule
description: Provides guidelines for generating conventional commit messages based on changes in the codebase. globs: /.
commit-message-format
description: Applies commit message standards to all files in the project. globs: /.