cursorrules

A repository rule that requires reading a shared documentation repository before making changes. It directs the agent to follow documentation branches, find existing patterns, and avoid duplicate material.

In plain words
What is it for?
Use it in repositories that depend on central docs, especially before changing code, creating documentation, selecting patterns, or adding reusable templates.
Why use it?
It helps development work follow the team’s established documentation and prevents new work from conflicting with or repeating existing guidance.

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/calibremcp/cursorrules
Clone the repo
git clone --depth 1 https://github.com/sandraschi/calibremcp

Made for: Cursor.

Per session 591 This file is loaded in full into every session.
When invoked 591 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00591 $0.00591
Opus 5 $0.00296 $0.00296
Sonnet 5 $0.00118 $0.00118
Haiku 4.5 $0.00059 $0.00059

Measured yesterday against content hash 90e4f7d207c0, 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.

.cursorrules · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 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:

  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.


Session Context (Calibre MCP)

You have access to a Calibre e-book library with 21 portmanteau tools for search, management, export, and RAG.

Read the full file on GitHub · 78 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. yesterday First seen · 78 lines · 591 tokens per session scan A 90e4f7d207c0

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository sandraschi/calibremcp (39 stars, last pushed 3d ago), licensed MIT. It adds 591 tokens to every session, about $0.0030 per session on Opus 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-30.