cursorrules

A set of rules for controlling a Godot 4 game-engine server. Godot is software for building games, and the server exposes tools for creating, exporting, publishing, and managing games.

In plain words
What is it for?
Use it when an agent needs to inspect Godot projects, build game content, export to HTML5, or prepare releases for itch.io or Steam.
Why use it?
It tells the agent which checks and save steps to perform while working with Godot projects.

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

Made for: Cursor.

Per session 123 This file is loaded in full into every session.
When invoked 123 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.00123 $0.00123
Opus 5 $0.00062 $0.00062
Sonnet 5 $0.00025 $0.00025
Haiku 4.5 $0.00012 $0.00012

Measured 2d ago against content hash 60dd6a9e9258, 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 2d 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.

.cursorrules · 12 lines

What it actually says

Session Context (Godot MCP)

You have access to a Godot 4 game engine control server with 49 tools across 10 domains: engine control, asset import/export, game building, fleet coordination, itch.io shipping, Steam publishing, animation, particles, HTML5 export, and cross-server MCP bridging.

Before starting work:

  1. Check server health: godot_status()
  2. List available projects: list_projects()
  3. Check Godot bridge connection: check_bridge_status()

At end of work, save findings:

  • Save any modified projects: save_project(project_id=...)
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. 2d ago First seen · 12 lines · 123 tokens per session scan A 60dd6a9e9258

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository sandraschi/godot-mcp (6 stars, last pushed 4d ago), licensed MIT. It adds 123 tokens to every session, about $0.0006 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-31.