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/dstotijn/mcp-origin/cursor-rules-locationgit clone --depth 1 https://github.com/dstotijn/mcp-originWhat 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.00322 | $0.00322 |
| Opus 5 | $0.00161 | $0.00161 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
cursor-rules-location 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.
This is a copy
100% identical to cursor-rules-location — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
description: Cursor Rules Location Rule globs: *.mdc
Description
This rule ensures that all new MDC (Model-Driven Code) rules are created in the .cursor/rules directory, maintaining a consistent and organized structure for rule management.
Rule
When creating new MDC rules:
- All new MDC rules MUST be created in the
.cursor/rulesdirectory - Each rule MUST be in a separate file
- Rule files MUST use the
.mdcextension - Rule files MUST follow the naming convention:
[rule-name].mdc - Rule files MUST contain proper markdown formatting
Implementation
- The Cursor IDE will enforce this rule by:
- Automatically creating new MDC rules in the
.cursor/rulesdirectory - Preventing creation of MDC rules outside this directory
- Maintaining separation of rules into individual files
- Ensuring proper file extensions and naming conventions
- Automatically creating new MDC rules in the
Benefits
- Improved organization and maintainability
- Easier rule discovery and management
- Consistent rule structure across the project
- Better version control and tracking of rule changes
Examples
✅ Correct:
.cursor/rules/
├── mdc-rules-location.mdc
├── another-rule.mdc
└── third-rule.mdc
❌ Incorrect:
.cursor/
├── rules/
│ └── mdc-rules-location.mdc
└── other-rules/
└── another-rule.mdc
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 · 45 lines · 322 tokens per session scan A 74e1af6c4b20
cursor-rules-location is a cursor rule published in the GitHub repository dstotijn/mcp-origin (5 stars, last pushed 1y ago), licensed Apache-2.0. It adds 322 tokens to every session, about $0.0016 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cursor-rules-location, differing in 4 lines, and is treated as a copy.
Other cursor rules, from other repositories
morpheus
Always-on rules for AI assistants working in this Morpheus Lumerin Node repo. Loaded automatically by Cursor.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.