Borrowing it
Nothing to install: this file belongs to sandraschi/database-operations-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/sandraschi/database-operations-mcp/master/.cursorrulesgit clone --depth 1 https://github.com/sandraschi/database-operations-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/sandraschi/database-operations-mcp/cursorrules)<a href="https://agentmods.dev/rules/sandraschi/database-operations-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/sandraschi/database-operations-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/sandraschi/database-operations-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/sandraschi/database-operations-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.00579 | $0.00579 |
| Opus 5.5 | $0.00232 | $0.00232 |
| Sonnet 5.5 | $0.00116 | $0.00116 |
| Haiku 4.5 | $0.00058 | $0.00058 |
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.
This is a copy
100% identical to cursorrules — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Central Documentation Rules
Rule #1: Read Central Docs First
BEFORE making any changes or starting work, ALWAYS:
-
Read the Central Documentation README:
- Location:
D:\Dev\repos\mcp-central-docs\README.md - This shows all important documentation "branches" (folder trees)
- Navigate from there to find specific information
- Location:
-
Follow Documentation Branches:
- Central docs are organized by topic (Anthropic ecosystem, Google ecosystem, patterns, projects, etc.)
- Each branch has its own README explaining what's inside
- Use the branch structure to find relevant docs
-
Check for Existing Patterns:
- Look in
docs/patterns/for design patterns - Check
templates/for reusable templates - Review
docs/projects/for similar project examples
- Look in
-
Avoid Duplication:
- Search existing docs before creating new ones
- Update existing docs rather than creating duplicates
- Reference central docs instead of copying content
Documentation Branches (from Central README)
Core Standards
STANDARDS.md- Documentation quality standardsSTRUCTURE.md- Directory layout guideCONTRIBUTING.md- How to contribute
Anthropic Ecosystem (docs/anthropic-ecosystem/)
- MCP Protocol, FastMCP, MCPB, Claude Desktop, Glama
Google Ecosystem (docs/google-ecosystem/)
- Gemini 3, Antigravity IDE, Nano Banana Pro, DeepMind, TPU infrastructure
Patterns (docs/patterns/)
- Design patterns for MCP servers and development
Projects (docs/projects/)
- myai, veogen, mywienerlinien, autohotkey
Monitoring (monitoring/)
- Prometheus/Grafana/Loki stack
Templates (templates/)
- Reusable templates and scripts
Quick Reference
Central Docs Location: D:\Dev\repos\mcp-central-docs\
Start Here: D:\Dev\repos\mcp-central-docs\README.md
When in doubt: Read the central README and navigate from there.
Session Context (database-operations-mcp)
Before starting work:
- Read
pyproject.toml(ports 10708/10709),src/database_operations_mcp/main.py, andweb_sota/vite.config.ts. - Use portmanteau tools:
db_connection(operation=...),db_operations(operation=...),db_schema(operation=...).
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 Changed · +10 lines · +112 tokens per session edd41c6e828d
- 1mo ago First seen · 64 lines · 467 tokens per session scan A 852d0c7811c4
cursorrules is a cursor rule published in the GitHub repository sandraschi/database-operations-mcp (3 stars, last pushed 6d ago), licensed MIT. It adds 579 tokens to every session, about $0.0023 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to cursorrules, differing in 15 lines, and is treated as a copy.
Other cursor rules, from other repositories
chdb
See CONTRIBUTING.md for the full contributor guide, including the crash-diagnosis rule (always capture the stack trace before changing code on SIGSEGV / SIGABRT / SIGFPE / SIGILL / SIGBUS / SIGSYS).
git-conventions
See CONTRIBUTING.md → "PR & commit conventions" for PR title format, commit messages, and branch naming.
chdb-ds
See AGENTS.md for chdb-ds design and testing principles.
python-general-best-practices
Python best practices and patterns for modern software development with Flask and SQLite.
sqlalchemy
SQLAlchemy database patterns and conventions.
JsonModel
This module provides the JsonModel class, a powerful Object-Relational Mapper (ORM)-like interface for storing and querying JSON-style documents within SQLite tables.