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/mrsuber/davinci-resolve-mcp/resolve-audiogit clone --depth 1 https://github.com/mrsuber/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/mrsuber/davinci-resolve-mcp/resolve-audio)<a href="https://agentmods.dev/rules/mrsuber/davinci-resolve-mcp/resolve-audio"><img src="https://agentmods.dev/badge/rules/mrsuber/davinci-resolve-mcp/resolve-audio.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 | $0.00047 | $0.00350 |
| Opus 5 | $0.00023 | $0.00175 |
| Sonnet 5 | $0.00009 | $0.00070 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
resolve-audio 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 4d 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.
This is a copy
100% identical to resolve-audio — 2 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.
What it actually says
Resolve Audio / Fairlight work. Apply when: setting audio properties, syncing audio, isolating voice, generating subtitles, planning Fairlight tracks/buses, checking loudness, routing buses, or splitting/trimming/converting audio.
Two servers — compute offline, apply live:
- Live (running Resolve,
davinci-resolve): timeline (probe_audio_item|track, safe_set_audio_properties, safe_auto_sync_audio, voice_isolation_capabilities, subtitle_generation_probe, fairlight_boundary_report) - Offline (.drp/.drt/.drx + DB, no Resolve,
davinci-resolve-advanced): audio_plan (track_plan, analyze_coverage, check_loudness), fairlight (bus routing — patches FLStudioModelBA, no scripting API), audio (split/trim/convert) - Key rule: Plan/measure offline, apply live. Bus routing has no scripting API — use fairlight (needs better-sqlite3; project CLOSED + quit/relaunch). audio ops need ffmpeg on PATH and write NEW files to scratch, never over source.
Depth: docs/kernels/audio-fairlight-kernel.md. On-demand in any MCP client: the /audio_workflow slash prompt. Claude Code skill: resolve-audio. Never modify/transcode/derive source media (AGENTS.md).
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.
- 4d ago First seen · 16 lines · 47 tokens per session scan A 2a1b4b6f5b00
resolve-audio is a cursor rule published in the GitHub repository mrsuber/davinci-resolve-mcp (0 stars, last pushed 29d ago), licensed MIT. It adds 47 tokens to every session and 350 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to resolve-audio, differing in 2 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.