documentation

documentation is a cursor rule for Cursor from brendadeeznuts1111/betting-brain-v3. It costs 0 tokens per session (654 once invoked), scanned A, original, MIT.

Rules for where documentation files belong, including folders for guides, testing, deployment, debugging, implementation, and archived material.

In plain words
What is it for?
Use them when placing guides, testing notes, deployment instructions, debugging material, implementation records, and historical documents.
Why use it?
They keep project information organized so developers can find instructions and status documents in predictable locations.

Cursor rule for Cursor

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

Good fit Use them when placing guides, testing notes, deployment instructions, debugging material, implementation records, and historical documents.

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

README.md
[![agentmods](https://agentmods.dev/badge/rules/brendadeeznuts1111/betting-brain-v3/documentation/github.svg)](https://agentmods.dev/rules/brendadeeznuts1111/betting-brain-v3/documentation)
Your own site
<a href="https://agentmods.dev/rules/brendadeeznuts1111/betting-brain-v3/documentation"><img src="https://agentmods.dev/badge/rules/brendadeeznuts1111/betting-brain-v3/documentation/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 documentation

Your own site · 80×15
<a href="https://agentmods.dev/rules/brendadeeznuts1111/betting-brain-v3/documentation"><img src="https://agentmods.dev/badge/rules/brendadeeznuts1111/betting-brain-v3/documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 654 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00654
Opus 5 $0.00000 $0.00327
Sonnet 5 $0.00000 $0.00131
Haiku 4.5 $0.00000 $0.00065

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

Security

Grade A, and why

documentation 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 9d 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/documentation.mdc · 96 lines

How it starts

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

Documentation Rules

File Placement

All documentation MUST be in the docs/ directory (except README.md, LICENSE, CLAUDE.md in root).

Directory Structure

docs/
├── guides/              # User guides and tutorials
├── testing/             # Testing documentation
├── deployment/          # Deployment guides
├── dashboards/          # Dashboard documentation
├── debug/               # Debugging guides
├── implementation/      # Technical implementation docs
└── archive/             # Historical/obsolete docs

Documentation Types

Status Files → docs/

docs/TESTING_STATUS.md
docs/MCP_INTEGRATION_STATUS.md
docs/AUTOMATION_GUIDE.md
docs/CODEBASE_REVIEW.md
docs/CLEANUP_SUMMARY.md

Guides → docs/guides/

docs/guides/START_HERE.md
docs/guides/DEBUGGING_DATA_CAPTURE.md
docs/guides/TESTING_GUIDE.md
docs/guides/AGENT_RISK_GUIDE.md

Testing → docs/testing/

docs/testing/TESTING_GUIDE.md
docs/testing/TEST_HEALTH_DASHBOARD.md
docs/testing/TEST_FAILURE_ANALYSIS.md

Archived → docs/archive/

docs/archive/phase-reports/
docs/archive/bun-upgrade/
docs/archive/mcp-integration/

Key Documentation Files

When Creating Documentation

  1. Choose the right location:

    • General docs → docs/
    • Guides/tutorials → docs/guides/
    • Testing docs → docs/testing/
    • Deployment → docs/deployment/
    • Old/obsolete → docs/archive/
  2. Never create in root (except README.md, LICENSE, CLAUDE.md)

  3. Update INDEX.md when adding significant docs

  4. Link between docs using relative paths:

    See [Testing Guide](testing/TESTING_GUIDE.md)
    See [Root Structure](ROOT_STRUCTURE.md)
    

Read the full file on GitHub · 96 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. 9d ago First seen · 96 lines · 0 tokens per session scan A 475159a48ee8

Subscribe to this mod's changes

documentation is a cursor rule published in the GitHub repository brendadeeznuts1111/betting-brain-v3 (8 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 654 tokens. 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.

Related

Other cursor rules, from other repositories