root-organization

root-organization is a cursor rule for Cursor from brendadeeznuts1111/betting-brain-v3. It costs 598 tokens per session, scanned A, original, MIT.

A set of rules for keeping the project's top-level folder small and organized. It lists which configuration and documentation files may be placed there and sends other documents, reports, tests, and build results to subfolders.

In plain words
What is it for?
Use it when adding or generating files in the repository. It tells you what belongs in the root and where to put documentation, status information, testing guides, backups, and build artifacts.
Why use it?
It prevents temporary files, status reports, generated output, and miscellaneous documentation from making the project root difficult to navigate. Clear placement rules make files easier to find and maintain.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions CLAUDE.md.

Good fit Use it when adding or generating files in the repository. It tells you what belongs in the root and where to put documentation, status information, testing guides, backups, and build artifacts.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/brendadeeznuts1111/betting-brain-v3/root-organization
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.

Clone the repo
git clone --depth 1 https://github.com/brendadeeznuts1111/betting-brain-v3

Made for: Cursor.

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.

agentmods badge for root-organization

README.md
[![agentmods](https://agentmods.dev/badge/rules/brendadeeznuts1111/betting-brain-v3/root-organization/github.svg)](https://agentmods.dev/rules/brendadeeznuts1111/betting-brain-v3/root-organization)
Your own site
<a href="https://agentmods.dev/rules/brendadeeznuts1111/betting-brain-v3/root-organization"><img src="https://agentmods.dev/badge/rules/brendadeeznuts1111/betting-brain-v3/root-organization/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for root-organization

Your own site · 80×15
<a href="https://agentmods.dev/rules/brendadeeznuts1111/betting-brain-v3/root-organization"><img src="https://agentmods.dev/badge/rules/brendadeeznuts1111/betting-brain-v3/root-organization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 598 This file is loaded in full into every session.
When invoked 598 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.1 $0.00598 $0.00598
Opus 5 $0.00299 $0.00299
Sonnet 5 $0.00120 $0.00120
Haiku 4.5 $0.00060 $0.00060

Measured 10d ago against content hash fe73519651c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

root-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 10d 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.

.cursor/rules/root-organization.mdc · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Root Directory Organization Rules

CRITICAL: Root Directory Policy

The root directory MUST remain clean and minimal.

✅ ALLOWED in Root

Only these files are permitted in the project root:

  • README.md - Main project documentation
  • LICENSE - Project license
  • CLAUDE.md - AI assistant guidance (like CONTRIBUTING.md)
  • package.json - Dependencies
  • package-lock.json - NPM lock file (auto-generated)
  • bun.lock - Bun lock file (auto-generated)
  • tsconfig.json - TypeScript configuration
  • wrangler.toml - Cloudflare Workers base config
  • wrangler.staging.toml - Staging environment config
  • wrangler.production.toml - Production environment config

❌ FORBIDDEN in Root

NEVER create these in root:

  • Markdown files (except README.md, LICENSE, CLAUDE.md)
  • Status files (MCP_INTEGRATION_STATUS.md, TESTING_STATUS.md, etc.)
  • Documentation files
  • Session summaries or reports
  • Cleanup plans or reviews
  • Temporary files
  • Test results or CI artifacts
  • Backup files (*.backup)
  • Build outputs
  • Coverage reports
  • Tilde directories (~, ~/)

File Placement Rules

Where Files Must Go

Documentation → docs/
Status files → docs/
Testing guides → docs/testing/ or docs/guides/
Deployment guides → docs/deployment/
Scripts → scripts/
Tools → tools/
Additional configs → config/
Archives → docs/archive/
Session reports → docs/
Reviews → docs/

Examples

❌ BAD: /TESTING_STATUS.md
✅ GOOD: /docs/TESTING_STATUS.md

❌ BAD: /MCP_INTEGRATION_STATUS.md
✅ GOOD: /docs/MCP_INTEGRATION_STATUS.md

❌ BAD: /CLEANUP_SUMMARY.md
✅ GOOD: /docs/CLEANUP_SUMMARY.md

❌ BAD: /setup-guide.md
✅ GOOD: /docs/guides/setup-guide.md

Before Creating ANY File

Ask yourself:

  1. Is this a standard project file? (package.json, README.md, LICENSE)
  2. Is this a required configuration? (tsconfig.json, wrangler.toml)
  3. If NO to both → It belongs in a subdirectory, NOT root!

Enforcement

See docs/ROOT_STRUCTURE.md for complete root directory reference.

Read the full file on GitHub · 86 lines

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. 10d ago First seen · 86 lines · 598 tokens per session scan A fe73519651c5

Subscribe to this mod's changes

root-organization is a cursor rule published in the GitHub repository brendadeeznuts1111/betting-brain-v3 (8 stars, last pushed 11mo ago), licensed MIT. It adds 598 tokens to every session, about $0.0030 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.