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/igamenovoer/davinci-resolve-mcp/cursorrulesgit clone --depth 1 https://github.com/igamenovoer/davinci-resolve-mcpWrote 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.
[](https://agentmods.dev/rules/igamenovoer/davinci-resolve-mcp/cursorrules)<a href="https://agentmods.dev/rules/igamenovoer/davinci-resolve-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/igamenovoer/davinci-resolve-mcp/cursorrules.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00392 | $0.00392 |
| Opus 5 | $0.00196 | $0.00196 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
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.
What it actually says
DaVinci Resolve MCP Server development rules for Cursor
Rules for the project
rules:
Quick navigation commands
-
name: View project structure match: /(project|structure|files)/i actions: ls -la
-
name: Show main server file match: /show (server|main|resolve_mcp_server)( file)?/i actions: cat resolve_mcp_server.py
-
name: Edit main server file match: /edit (server|main|resolve_mcp_server)( file)?/i actions: open resolve_mcp_server.py
Run commands
-
name: Run server in dev mode match: /run( server)?( in dev)?/i actions: ./run-now.sh
-
name: Setup server match: /setup( server)?/i actions: ./setup.sh
View logs and instructions
-
name: Show README match: /show readme/i actions: cat README.md
-
name: View changelog match: /show changelog/i actions: cat CHANGELOG.md
DaVinci Resolve specific
-
name: Check Resolve environment match: /check (resolve|environment|env|paths)/i actions: | echo "RESOLVE_SCRIPT_API = $RESOLVE_SCRIPT_API" echo "RESOLVE_SCRIPT_LIB = $RESOLVE_SCRIPT_LIB" echo "PYTHONPATH = $PYTHONPATH"
-
name: Check if Resolve is running match: /is resolve running/i actions: ps -ef | grep -i "[D]aVinci Resolve"
Directory settings
directories:
Ignore virtual environment folder in searches
- path: venv excludeFromSearch: true
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.
- 5d ago First seen · 52 lines · 392 tokens per session scan A 826f3a45debf
cursorrules is a cursor rule published in the GitHub repository igamenovoer/davinci-resolve-mcp (0 stars, last pushed 10mo ago), licensed MIT. It adds 392 tokens to every session, about $0.0020 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.