Borrowing it
Nothing to install: this file belongs to brendadeeznuts1111/betting-brain-v3. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/brendadeeznuts1111/betting-brain-v3/main/.cursorrulesgit clone --depth 1 https://github.com/brendadeeznuts1111/betting-brain-v3Wrote 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/brendadeeznuts1111/betting-brain-v3/cursorrules)<a href="https://agentmods.dev/rules/brendadeeznuts1111/betting-brain-v3/cursorrules"><img src="https://agentmods.dev/badge/rules/brendadeeznuts1111/betting-brain-v3/cursorrules.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.00000 | $0.02026 |
| Opus 5 | $0.00000 | $0.01013 |
| Sonnet 5 | $0.00000 | $0.00405 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
cursorrules 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 7d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor AI Rules for Betting Brain Platform
https://github.com/nolarose1968/ffffff/blob/main/.cursorrules
One File to Rule Them All
This .cursorrules file is the single source of truth for all AI-generated code.
Benefits:
- ✅ No confusion - everyone follows the same patterns
- ✅ Version control - every change is tracked
- ✅ Automatic application - Cursor applies rules to matching files
- ✅ Machine readable - front-matter enables tooling integration
Alternative: Cursor ≥ 0.45 also supports .cursor/rules/ folder for larger projects.
Core Development Rules
Bun Runtime (CRITICAL)
- Use
buncommands exclusively (not npm/yarn/node) - Use Bun Test (not Vitest/Jest)
- Use Bun file APIs (not Node.js fs)
- Use processManager for all process spawning
- Leverage Bun native APIs (crypto, compression, etc.)
File Organization
- Root directory: Only 9 essential files allowed
- Documentation: All docs in
docs/(except README.md, LICENSE, CLAUDE.md) - Scripts: All in
scripts/ - Tools: All in
tools/ - Status files: All in
docs/
File Naming
- Use lowercase kebab-case for all files/directories
- Test files:
*.test.ts(preferred) - Special cases: MCP handlers use camelCase to match tool names
- Never create backup files (*.backup, *.old, *.bak)
API & Endpoint Patterns
Request Handling
- Always generate requestId:
Date.now().toString(36) - Always include CORS headers for dashboard access
- Always handle OPTIONS preflight requests
- Always log with requestId prefix:
[${requestId}] ...
Error Handling
- Use standardized error classes from
src/utils/error-handler.ts - Always use try-catch or asyncHandler wrapper
- Always return structured error responses
- Never expose internal details in error messages
Database Queries
- Always use parameterized queries (
.bind()) - Never use string interpolation in SQL
- Always cast D1 results with
as unknown as - Always handle database errors
Security Patterns
Input Validation
- Always validate all inputs before processing
- Use Zod schemas for request validation
- Never trust user input
- Always sanitize output to prevent XSS
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.
- 7d ago First seen · 245 lines · 0 tokens per session scan A 42d31a67bb9a
cursorrules 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 2,026 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.
Other cursor rules, from other repositories
workers-patterns
Skim this on every task that touches workers, env, routes, or bindings.
typescript-imports
Golden rule: import each symbol from the module that defines it. A package index.ts may barrel only its own ./ modules — never another package.
git-workflow
Cloud Agents MUST run git add, git commit, and git push before ending their response when they have made code changes. Do not end your turn without pushing. ALWAYS use Pull Requests instead of pushing directly to main.
dev-server
Do not start dev servers or long-running watch processes unless the user explicitly asks (e.g. “run dev”, “verify in the browser”). If they do, use the project’s bun run dev from the repo root and stop or ask before leaving a server running forever.
generated-artifacts
Agents must not manually author generated files. If generated output needs to change, edit the source-of-truth file and run the generator. If the generator fails, fix the source or generator instead of fabricating output.
new-env-var-checklist
Checklist when adding any new env secret/variable — Turbo globalEnv, GitHub sync, workflow maps, Alchemy bindings. Prevents "secret synced but worker never gets it".