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.
npx agentmods add rules/sandraschi/grandorgue-mcp/cursorrulesgit clone --depth 1 https://github.com/sandraschi/grandorgue-mcpWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00145 | $0.00145 |
| Opus 5 | $0.00072 | $0.00072 |
| Sonnet 5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00015 | $0.00015 |
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.
What it actually says
grandorgue-mcp rules
Session Context (GrandOrgue MCP)
You have access to a GrandOrgue pipe organ simulator MCP server with 30 tools for MIDI bridge, organ control, sample set management, and Bach repertoire.
Before starting work, check organ status:
- Check current state:
go_status— see if GrandOrgue is running, MIDI is connected, and what organ is loaded - Query MIDI ports:
go_list_midi_ports— list available MIDI input/output ports
At end of work, save state:
- If you loaded an organ, note it for next session
- If you changed settings, remember they persist in settings_store
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.
- 2d ago First seen · 14 lines · 145 tokens per session scan A 0789309c72ca
cursorrules is a cursor rule published in the GitHub repository sandraschi/grandorgue-mcp (2 stars, last pushed 5d ago), licensed MIT. It adds 145 tokens to every session, about $0.0007 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.
Other cursor rules, from other repositories
technical-writing
You are an AI writing assistant specialized in creating exceptional technical documentation for the JamfMCP project using Sphinx with MyST Parser, sphinx-design, and pydata-sphinx-theme.
cursorrules
Composite MCP server for AI-powered music production workflows. Mounts and orchestrates multiple MCP servers (VirtualDJ, Plex, Suno, Reaper, OBS).
cursorrules
You have access to an MCP server that automates Notepad++ on Windows: fileops, textops, tabops, sessionops, lintingops, displayops, pluginops, statusops (portmanteau tools with an operation enum).
cursorrules
FastMCP server + webapp that bridges Claude Desktop / Cursor to OpenClaw (agent Gateway, channels, routing, sessions, skills, security) and Moltbook (AI-agent social network). It uses those platforms; it does not implement or replace them.
cursorrules
You are working on stripe-mcp, an MCP server and SOTA React webapp providing Stripe payment tools and Austrian/EU tax compliance.
cursorrules
BEFORE making any changes or starting work, ALWAYS.