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/elirancv/cursormd/file-organizationgit clone --depth 1 https://github.com/elirancv/CursorMDWrote 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/elirancv/cursormd/file-organization)<a href="https://agentmods.dev/rules/elirancv/cursormd/file-organization"><img src="https://agentmods.dev/badge/rules/elirancv/cursormd/file-organization.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 | $0.01587 | $0.01587 |
| Opus 5 | $0.00794 | $0.00794 |
| Sonnet 5 | $0.00317 | $0.00317 |
| Haiku 4.5 | $0.00159 | $0.00159 |
Grade A, and why
file-organization 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 4d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Organization & Project Structure
Maintain perfect project organization. Never create files in wrong locations.
Critical Rule: Ask Before Writing
ALWAYS ask the user before creating/writing files:
- Show summary first - Display the document content in chat
- Ask for confirmation - "Should I create this file at [location]?"
- Wait for explicit approval - Only write files after user confirms
- Respect user's choice - If they say "just show me", don't write files
Exception: Only write files automatically if user explicitly says "create", "write", "save", or "generate file".
File Placement Rules
Root Directory Files (Only These)
Allowed in root:
README.md- Project overviewPROJECT_EVALUATION.md- Project assessmentCONTRIBUTING.md- Contribution guidelinesCHANGELOG.md- Version historyLICENSE- License file.gitignore- Git ignore rules.cursorrules- Cursor rules (legacy)- Configuration files (
.env.example,package.json, etc.)
NEVER create in root:
- ❌ Scripts (use
scripts/directory) - ❌ Tools or utilities (use
scripts/ortools/directory) - ❌ Documentation files (except README.md, PROJECT_EVALUATION.md, CONTRIBUTING.md, CHANGELOG.md)
- ❌ Architecture documents
- ❌ Technical specs
- ❌ Any other .md files (except allowed ones above)
Documentation Directory Structure
Standard structure:
project-root/
├── README.md # ✅ Root (allowed)
├── PROJECT_EVALUATION.md # ✅ Root (allowed)
├── CONTRIBUTING.md # ✅ Root (allowed)
├── docs/ # ✅ All other docs go here
│ ├── ARCHITECTURE_OVERVIEW.md
│ ├── PRD_MVP.md
│ ├── TECH_SPEC_MVP.md
│ ├── VISION.md
│ └── ... (all other docs)
└── ... (other project files)
Document Type → Location Mapping
| Document Type | Location | Notes |
|---|---|---|
| README.md | Root | ✅ Always root |
| PROJECT_EVALUATION.md | Root | ✅ Always root |
| CONTRIBUTING.md | Root | ✅ Always root |
| VISION.md | docs/ |
✅ docs/ |
| PRD_*.md | docs/ |
✅ docs/ |
| ARCHITECTURE_*.md | docs/ |
✅ docs/ |
| TECH_SPEC_*.md | docs/ |
✅ docs/ |
| PIPELINE_*.md | docs/ |
✅ docs/ |
| All other docs | docs/ |
✅ docs/ |
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.
- 4d ago First seen · 201 lines · 1,587 tokens per session scan A 783de262d5ab
file-organization is a cursor rule published in the GitHub repository elirancv/CursorMD (1 stars, last pushed 9mo ago), licensed MIT. It adds 1,587 tokens to every session, about $0.0079 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-08-31.
Other cursor rules, from other repositories
create-rule-agent
This rule is responsible for creating and updating Cursor rules. Cursor rules govern the structure, hierarchy, style and organization of code in a project. This rule should be invoked in Agent mode when: 1. a user wants to create a new cursor rule, 2. a user wants to update or change an existing rule, 3. user wants…
cloudflare-workers-hono-auto
Cloudflare Workers with Hono framework development standards and best practices.
security-scan-agent
This rule provides comprehensive security scanning for dependencies, complementing the dependency analysis rule with deep security insights including CVE analysis, license compliance, and supply chain risk assessment.
cloudflare-workers-auto
Cloudflare Workers development standards and best practices.
changelog-generator-manual
This rule generates a comprehensive changelog.md file by analyzing all git tags and commits, creating a chronological record of all project changes with proper semantic versioning structure. The changelog.md file is stored at the root of the project.
mysql-auto
This rule enforces MySQL-specific best practices to enhance readability, performance, security, and maintainability. It targets MySQL features (e.g., storage engines, character sets) and common pitfalls, and adds concrete guidance for schema design and creation.