cursor-rules-location

Repository rules for Cursor rule files, which are Markdown files ending in .mdc that guide the Cursor coding editor. They require these files to live in the project's .cursor/rules directory and use kebab-case names.

In plain words
What is it for?
Use them when creating or organizing Cursor rules in a repository.
Why use it?
They prevent rule files from being created in the wrong place or with inconsistent names.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/squirrelogic/mcp-feature-discussion/cursor-rules-location
Clone the repo
git clone --depth 1 https://github.com/squirrelogic/mcp-feature-discussion

Made for: Cursor.

Per session 470 This file is loaded in full into every session.
When invoked 470 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 89% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00470 $0.00470
Opus 5 $0.00235 $0.00235
Sonnet 5 $0.00094 $0.00094
Haiku 4.5 $0.00047 $0.00047

Measured yesterday against content hash 7bc5c03b11ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

Origin

This is a copy

89% identical to cursor-rules-location — 13 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.

.cursor/rules/cursor-rules-location.mdc · 73 lines

What it actually says

Cursor Rules Location

Rules for placing and organizing Cursor rule files in the repository. name: cursor_rules_location description: Standards for placing Cursor rule files in the correct directory filters:

Match any .mdc files

  • type: file_extension pattern: "\.mdc$"

Match files that look like Cursor rules

  • type: content pattern: "(?s).*?"

Match file creation events

  • type: event pattern: "file_create"

actions:

  • type: reject conditions:

    • pattern: "^(?!\.\/\.cursor\/rules\/.*\.mdc$)" message: "Cursor rule files (.mdc) must be placed in the .cursor/rules directory"
  • type: suggest message: | When creating Cursor rules:

    1. Always place rule files in PROJECT_ROOT/.cursor/rules/:

      .cursor/rules/
      ├── your-rule-name.mdc
      ├── another-rule.mdc
      └── ...
      
    2. Follow the naming convention:

      • Use kebab-case for filenames
      • Always use .mdc extension
      • Make names descriptive of the rule's purpose
    3. Directory structure:

      PROJECT_ROOT/
      ├── .cursor/
      │   └── rules/
      │       ├── your-rule-name.mdc
      │       └── ...
      └── ...
      
    4. Never place rule files:

      • In the project root
      • In subdirectories outside .cursor/rules
      • In any other location

examples:

  • input: |

    Bad: Rule file in wrong location

    rules/my-rule.mdc my-rule.mdc .rules/my-rule.mdc

    Good: Rule file in correct location

    .cursor/rules/my-rule.mdc output: "Correctly placed Cursor rule file"

metadata: priority: high version: 1.0

Changes

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.

  1. yesterday First seen · 73 lines · 470 tokens per session scan A 7bc5c03b11ae

Subscribe to this mod's changes

cursor-rules-location is a cursor rule published in the GitHub repository squirrelogic/mcp-feature-discussion (1 stars, last pushed 1y ago), licensed MIT. It adds 470 tokens to every session, about $0.0024 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to cursor-rules-location, differing in 13 lines, and is treated as a copy.