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/ivangrynenko/cursorrules/cursor-rulesgit clone --depth 1 https://github.com/ivangrynenko/cursorrulesWhat 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.00707 |
| Opus 5 | $0.00000 | $0.00353 |
| Sonnet 5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
cursor-rules 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 2d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Rules Location
Standards for placing and organizing Cursor rule files in the repository, ensuring rules are always up-to-date and follow best practices.
Rule Details
-
Name: cursor_rules_location_and_maintenance
-
Description: Standards for placing and maintaining Cursor rule files in the correct directory
Filters
- file extension pattern:
\\.mdc$- Match files that look like Cursor rules
- content:
(?s)<rule>.*?</rule>- Match file creation or modification events
- event:
file_create|file_modify
Rejections
- Conditions:
- pattern
^(?!\\.\\/\\.cursor\\/rules\\/.*\\.mdc$)– Cursor rule files (.mdc) must be placed in the .cursor/rules directory
- pattern
Suggestions
- Guidance:
Cursor Rules Best Practices
1. Location and Structure
- Location: Always place rule files in PROJECT_ROOT/.cursor/rules/
- Directory Structure:
PROJECT_ROOT/ ├── .cursor/ │ └── rules/ │ ├── your-rule-name.mdc │ └── ... └── ...
2. Naming Conventions
- Use kebab-case for filenames (e.g.,
php-drupal-standards.mdc) - Always use the .mdc extension
- Make names descriptive of the rule's purpose
- Group related rules with common prefixes (e.g.,
drupal-*,lagoon-*)
3. Rule File Structure
---
description: Brief description of the rule
globs: *.php, *.module, *.inc
alwaysApply: false
---
# Rule Title
<rule>
name: rule_name_in_snake_case
description: Detailed description of what the rule enforces
filters:
- type: file_extension
pattern: "pattern_to_match"
actions:
- type: enforce|suggest|validate
conditions:
- pattern: "regex_pattern"
message: "Clear message explaining the issue"
metadata:
priority: high|medium|low
version: 1.1
</rule>
4. Rule Maintenance
- When adding new rules:
- Check for overlapping or conflicting rules
- Ensure patterns are efficient and specific
- Test rules against sample code
- When modifying existing rules:
- Update version number
- Document changes in commit messages
- Review and update related rules for consistency
- Consider backward compatibility
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.
- 2d ago First seen · 106 lines · 707 tokens per session scan A 6675e7e1b1e1
cursor-rules is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (87 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 707 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-30.
Other cursor rules, from other repositories
angular
Angular: signals, standalone components, RxJS patterns.
django
Django: models, views, ORM best practices.
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.
rust
Rust patterns: ownership, Result types, iterators.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.