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/markmhendrickson/neotoma/cursor_rules_editinggit clone --depth 1 https://github.com/markmhendrickson/neotomaWrote 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/markmhendrickson/neotoma/cursor_rules_editing)<a href="https://agentmods.dev/rules/markmhendrickson/neotoma/cursor_rules_editing"><img src="https://agentmods.dev/badge/rules/markmhendrickson/neotoma/cursor_rules_editing.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.00038 | $0.01027 |
| Opus 5 | $0.00019 | $0.00513 |
| Sonnet 5 | $0.00008 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
cursor_rules_editing 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ DO NOT EDIT THIS FILE DIRECTLY
This is a copy of: foundation/agent_instructions/cursor_rules/cursor_rules_editing.mdc
Source of truth: foundation/agent_instructions/cursor_rules/cursor_rules_editing.mdc
To edit this rule:
1. Edit the source file: foundation/agent_instructions/cursor_rules/cursor_rules_editing.mdc
2. Run '/setup_cursor_copies' to sync changes
This file will be overwritten when running setup_cursor_copies.
Cursor Rules Editing Rule
Purpose
Ensures agents always edit the source files for cursor rules and commands, never the copies in .cursor/rules/ or .cursor/commands/ directories.
Source of Truth Locations
Foundation rules and commands:
- Source:
foundation/agent_instructions/cursor_rules/andfoundation/agent_instructions/cursor_commands/ - Copies:
.cursor/rules/and.cursor/commands/(created by/setup_cursor_copies)
Repository rules:
- Source:
docs/subdirectories (e.g.,docs/foundation/,docs/conventions/,docs/developer/) - Copies:
.cursor/rules/(created by/setup_cursor_copies)
Repository commands:
- Source:
docs/subdirectories or repository-specific command locations - Copies:
.cursor/commands/(created by/setup_cursor_copies)
Rule
MUST NOT edit files in .cursor/rules/ or .cursor/commands/
These directories contain copies that are:
- Automatically generated by
/setup_cursor_copies - Overwritten when running
/setup_cursor_copies - Not the source of truth
Agent Actions
When Editing Rules or Commands
-
Identify the source file:
- Foundation rules:
foundation/agent_instructions/cursor_rules/{name}.mdc - Foundation commands:
foundation/agent_instructions/cursor_commands/{name}.md - Repository rules:
docs/{subdirectory}/{name}_rules.mdcordocs/{subdirectory}/{name}_rules.md - Repository commands:
docs/{subdirectory}/{name}_command.mdor repository-specific command locations
- Foundation rules:
-
Edit the source file directly
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 · 100 lines · 38 tokens per session scan A ed0b8bce0c42
cursor_rules_editing is a cursor rule published in the GitHub repository markmhendrickson/neotoma (31 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 1,027 once invoked, about $0.0002 per session on Opus 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-09-03.
Other cursor rules, from other repositories
atomicmemory
AtomicMemory persistent memory protocol and MCP tool usage.
gctrl
GCTRL long-term memory over MCP. Apply before answering any factual question about the user's organization, projects, people, systems, decisions, history, or file locations (unfamiliar proper nouns, "our/we" references, "what do we know about X"), and after substantive work to write conclusions back.
lemoncrow.execute
LemonCrow execute mode reference for Cursor.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.