Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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_sync_requirement)<a href="https://agentmods.dev/rules/markmhendrickson/neotoma/cursor_rules_sync_requirement"><img src="https://agentmods.dev/badge/rules/markmhendrickson/neotoma/cursor_rules_sync_requirement.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.00032 | $0.01268 |
| Opus 5 | $0.00016 | $0.00634 |
| Sonnet 5 | $0.00006 | $0.00254 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
cursor_rules_sync_requirement 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 — 156 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_sync_requirement.mdc
Source of truth: foundation/agent_instructions/cursor_rules/cursor_rules_sync_requirement.mdc
To edit this rule:
1. Edit the source file: foundation/agent_instructions/cursor_rules/cursor_rules_sync_requirement.mdc
2. Run '/setup_cursor_copies' to sync changes
This file will be overwritten when running setup_cursor_copies.
Cursor Rules Sync Requirement Rule
Purpose
Ensures agents ALWAYS run /setup_cursor_copies immediately after updating any rule or command file, ensuring changes are synced to .cursor/ directory in the same conversation/workflow.
Scope
This document covers:
- Mandatory requirement to run
/setup_cursor_copiesafter rule/command updates - When this requirement applies
- Validation requirements
This document does NOT cover:
- How to edit rules (see
cursor_rules_editing.mdc) - Foundation vs repository rule locations (see
cursor_rules_editing.mdc)
Trigger Patterns
Agents MUST run /setup_cursor_copies immediately after:
- Editing any file in
docs/that is a rule source (files matching*_rules.mdcor*_rules.md) - Editing any file in
docs/that is a command source (files matching*_command.md) - Editing any file in
foundation/agent_instructions/cursor_rules/ - Editing any file in
foundation/agent_instructions/cursor_commands/ - Updating rule documentation
- Creating new rule files
- Modifying existing rule files
Mandatory Requirement
MANDATORY: After editing ANY rule or command source file, agents MUST:
- Immediately run
/setup_cursor_copiesin the same conversation/workflow - Do NOT defer this step to a later conversation
- Do NOT mark rule updates complete without running
/setup_cursor_copies - Verify the sync succeeded by checking script output
Agent Actions
Step 1: Edit Source File
- Identify the source file location:
- Repository rules:
docs/{subdirectory}/{name}_rules.mdcordocs/{subdirectory}/{name}_rules.md - Foundation rules:
foundation/agent_instructions/cursor_rules/{name}.mdc - Commands:
docs/{subdirectory}/{name}_command.mdorfoundation/agent_instructions/cursor_commands/{name}.md
- Repository rules:
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 · 156 lines · 32 tokens per session scan A e14867b6b8d0
cursor_rules_sync_requirement is a cursor rule published in the GitHub repository markmhendrickson/neotoma (31 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 1,268 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
git-conventions
Git commit message conventions and PR merge strategy for jentic-one.
atomicmemory
AtomicMemory persistent memory protocol and MCP tool usage.
cairn-commit-network
Commits that run cairn hooks need unsandboxed network.
git-conventions
Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.
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.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.