cursorrules

cursorrules is a cursor rule for Cursor from toasted-iron-studios/godot-agent-mcp. It costs 894 tokens per session, scanned A, original, MIT.

Coding rules for a Godot MCP project, where MCP is a standard way for AI tools to use software capabilities. They require clear code, docblocks for public functions, and no inline comments inside function bodies.

In plain words
What is it for?
Writing or reviewing Godot project code, including public functions, classes, parameters, return values, and error documentation.
Why use it?
They set consistent expectations for readable code and documentation, especially when code needs explanation.

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/toasted-iron-studios/godot-agent-mcp/cursorrules
Clone the repo
git clone --depth 1 https://github.com/toasted-iron-studios/godot-agent-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/toasted-iron-studios/godot-agent-mcp/cursorrules.svg)](https://agentmods.dev/rules/toasted-iron-studios/godot-agent-mcp/cursorrules)
Your own site
<a href="https://agentmods.dev/rules/toasted-iron-studios/godot-agent-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/toasted-iron-studios/godot-agent-mcp/cursorrules.svg" alt="Measured on agentmods" height="20"></a>
Per session 894 This file is loaded in full into every session.
When invoked 894 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.00894 $0.00894
Opus 5 $0.00447 $0.00447
Sonnet 5 $0.00179 $0.00179
Haiku 4.5 $0.00089 $0.00089

Measured 5d ago against content hash 6fec2b9ff6cb, 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 5d 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 · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cursor Rules for Godot Agent MCP Project

Code Quality Standards

NO INLINE COMMENTS

  • NEVER use inline comments (single # comments within function bodies)
  • Inline comments indicate poor code quality and lack of experience
  • If code needs explanation, refactor it into a well-named function with a docblock
  • Code should be self-documenting through clear variable and function names

Commenting Standards

  • ONLY use docblock comments (## comments) for function/class documentation
  • Docblocks should describe WHAT the function does, not HOW it does it
  • Focus on the purpose, parameters, return values, and side effects
  • No redundant comments that just repeat what the code obviously does

MANDATORY DOCBLOCKS

  • ALL public functions MUST have descriptive docblocks
  • Docblocks must explain the function's purpose, parameters, return values, and side effects
  • Private functions (starting with _) should have docblocks if their purpose isn't immediately obvious
  • Include parameter types and return types in the description when helpful
  • Document any exceptions or error conditions the function might encounter

Code Structure

  • If logic is complex enough to "need" inline comments, extract it to a separate function
  • Use descriptive variable and function names that make the code self-explanatory
  • Prefer small, focused functions with clear responsibilities
  • Break down complex operations into well-named helper functions

Examples of BAD commenting:

# Parse the request data  <-- NEVER DO THIS
var data = parse_request(request)

# Check if user is valid  <-- NEVER DO THIS  
if user.is_valid():
    # Process the user  <-- NEVER DO THIS
    process_user(user)

Examples of GOOD commenting:

## Validates user credentials and processes authentication request
## Returns true if authentication succeeds, false otherwise
func authenticate_user(credentials: Dictionary) -> bool:
    var user = find_user_by_credentials(credentials)
    if not user or not user.is_valid():
        return false
    
    return process_authentication(user)

## Converts raw HTTP request data into a structured request object
## Parameters:
##   - raw_data: The complete HTTP request as a string
## Returns: Dictionary containing parsed headers, body, and method
## Throws: Returns error dictionary if request format is invalid
func parse_http_request(raw_data: String) -> Dictionary:
    # Implementation here

Read the full file on GitHub · 99 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. 5d ago First seen · 99 lines · 894 tokens per session scan A 6fec2b9ff6cb

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository toasted-iron-studios/godot-agent-mcp (11 stars, last pushed 1y ago), licensed MIT. It adds 894 tokens to every session, about $0.0045 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.