virtualization-mcp: Cursor rule for Cursor

.cursorrules

cursorrules is a cursor rule for Cursor from sandraschi/virtualization-mcp. It costs 523 tokens per session, scanned A, a copy of cursorrules, MIT.

A set of rules requiring an AI coding assistant to read a central documentation repository before making changes. The documentation contains project standards, reusable patterns, templates, and examples.

In plain words
What is it for?
Use it at the start of development or documentation work when the project depends on the specified central documentation repository.
Why use it?
It helps the assistant follow existing project decisions and avoid creating duplicate documentation or inconsistent implementations.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

This is sandraschi/virtualization-mcp's own configuration. It tells Cursor how to work on virtualization-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything virtualization-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sandraschi/virtualization-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.

Copy the file
curl -O https://raw.githubusercontent.com/sandraschi/virtualization-mcp/master/.cursorrules
Clone the repo
git clone --depth 1 https://github.com/sandraschi/virtualization-mcp

Made for: Cursor.

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

agentmods badge for cursorrules

README.md
[![agentmods](https://agentmods.dev/badge/rules/sandraschi/virtualization-mcp/cursorrules/github.svg)](https://agentmods.dev/rules/sandraschi/virtualization-mcp/cursorrules)
Your own site
<a href="https://agentmods.dev/rules/sandraschi/virtualization-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/sandraschi/virtualization-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.

agentmods 80×15 button for cursorrules

Your own site · 80×15
<a href="https://agentmods.dev/rules/sandraschi/virtualization-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/sandraschi/virtualization-mcp/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 523 This file is loaded in full into every session.
When invoked 523 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00523 $0.00523
Opus 5.5 $0.00209 $0.00209
Sonnet 5.5 $0.00105 $0.00105
Haiku 4.5 $0.00052 $0.00052

Measured 8d ago against content hash 3fe544297f19, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 8d 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.

Origin

This is a copy

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

.cursorrules · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 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 (virtualization-mcp)

Before starting work: list VMs via vm_management(action="list") to ground names/state. At end of work: run ruff check src/ + pytest tests/ -q, update CHANGELOG.md.

Read the full file on GitHub · 70 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. 8d ago Changed · +6 lines · +56 tokens per session 3fe544297f19
  2. 1mo ago 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/virtualization-mcp (16 stars, last pushed 4d ago), licensed MIT. It adds 523 tokens to every session, about $0.0021 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to cursorrules, differing in 11 lines, and is treated as a copy.