cursorrules

A rule requiring work to begin by reading a central documentation repository and following its topic branches, patterns, templates, and project examples.

In plain words
What is it for?
Use it before making changes that depend on shared documentation, reusable patterns, templates, standards, or related project examples.
Why use it?
It helps keep documentation work consistent, find existing guidance, and avoid creating duplicate material.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/sandraschi/database-operations-mcp/cursorrules
Clone the repo
git clone --depth 1 https://github.com/sandraschi/database-operations-mcp

Made for: Cursor.

Per session 467 This file is loaded in full into every session.
When invoked 467 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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 $0.00467 $0.00467
Opus 5 $0.00234 $0.00234
Sonnet 5 $0.00093 $0.00093
Haiku 4.5 $0.00047 $0.00047

Measured yesterday against content hash 852d0c7811c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

Origin

This is a copy

100% identical to cursorrules — 1 line 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.

.cursorrules · 64 lines

What it actually says

Central Documentation Rules

Rule #1: Read Central Docs First

BEFORE making any changes or starting work, ALWAYS:

  1. 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
  2. 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
  3. Check for Existing Patterns:

    • Look in docs/patterns/ for design patterns
    • Check templates/ for reusable templates
    • Review docs/projects/ for similar project examples
  4. 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 standards
  • STRUCTURE.md - Directory layout guide
  • CONTRIBUTING.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.

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. yesterday First seen · 64 lines · 467 tokens per session scan A 852d0c7811c4

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository sandraschi/database-operations-mcp (3 stars, last pushed 14d ago), licensed MIT. It adds 467 tokens to every session, about $0.0023 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cursorrules, differing in 1 line, and is treated as a copy.