Borrowing it
Nothing to install: this file belongs to yusakuvol/betting-method-mcp. 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/yusakuvol/betting-method-mcp/main/.cursorrulesgit clone --depth 1 https://github.com/yusakuvol/betting-method-mcpWrote 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/yusakuvol/betting-method-mcp/cursorrules)<a href="https://agentmods.dev/rules/yusakuvol/betting-method-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/yusakuvol/betting-method-mcp/cursorrules/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.
<a href="https://agentmods.dev/rules/yusakuvol/betting-method-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/yusakuvol/betting-method-mcp/cursorrules.svg" alt="Reviewed on agentmods" width="80" 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.01427 | $0.01427 |
| Opus 5.5 | $0.00571 | $0.00571 |
| Sonnet 5.5 | $0.00285 | $0.00285 |
| Haiku 4.5 | $0.00143 | $0.00143 |
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 1mo 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor/Codex Rules for betting-method-mcp
Project Type
TypeScript MCP (Model Context Protocol) server for betting method calculations
Stack
- TypeScript (strict mode)
- Node.js >= 18
- MCP SDK
- Vitest (testing)
- Biome (linter/formatter)
Code Style (Enforced by Biome)
- Double quotes ALWAYS
- Semicolons ALWAYS
- 2 space indentation
- 100 character line width
- Trailing commas everywhere
- Arrow function parentheses always
Naming Rules
- Classes: PascalCase (MonteCarloMethod)
- Interfaces: PascalCase + "State" suffix (MonteCarloState)
- Functions: camelCase (recordResult, initSession)
- MCP tools: lowercase_underscore (montecarlo_init)
- Files: lowercase (montecarlo.ts, martingale.ts)
Architecture Pattern
Every betting method class MUST have:
private state: MethodStatepropertyconstructor()- default initializationinitSession(params)- setup with validationrecordResult(result: "win" | "loss")- update logicgetState()- return COPY of state (immutability!)reset()- restart session
Every state interface MUST:
- Extend
BettingMethodState - Include these required properties:
- currentBet: number
- totalProfit: number
- sessionActive: boolean
Every MCP method MUST register 4 tools:
- {method}_init
- {method}_record
- {method}_status
- {method}_reset
Critical Rules
✅ ALWAYS DO:
- Validate ALL parameters in initSession()
- Check sessionActive before recordResult()
- Return state COPY from getState() using spread:
{ ...this.state } - Use double quotes for strings
- Add semicolons to every statement
- Write comprehensive tests (8+ test cases per method)
- Throw descriptive errors with actionable messages
- Update totalProfit in recordResult()
❌ NEVER DO:
- Return state directly from getState() (breaks immutability)
- Skip parameter validation
- Modify state without creating new object
- Use single quotes
- Omit semicolons
- Process results without checking sessionActive
- Write vague error messages
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.
- 1mo ago First seen · 252 lines · 1,427 tokens per session scan A e0c9f91c6975
cursorrules is a cursor rule published in the GitHub repository yusakuvol/betting-method-mcp (0 stars, last pushed 7mo ago), licensed MIT. It adds 1,427 tokens to every session, about $0.0057 per session on Opus 5.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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.