davinci-resolve-mcp is an MCP server that lets AI assistants control DaVinci Resolve Studio through its scripting API, including editing, media organization, rendering, grading, and other project tasks. It is for users who want agents to operate Resolve and inspect media through a local control panel. The catalogue entries support agent workflows for this Resolve integration.
Borrowing it
Nothing to install: this file belongs to samuelgursky/davinci-resolve-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/samuelgursky/davinci-resolve-mcp/main/.github/instructions/resolve-audio.instructions.mdgit clone --depth 1 https://github.com/samuelgursky/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/instructions/samuelgursky/davinci-resolve-mcp/resolve-audio)<a href="https://agentmods.dev/instructions/samuelgursky/davinci-resolve-mcp/resolve-audio"><img src="https://agentmods.dev/badge/instructions/samuelgursky/davinci-resolve-mcp/resolve-audio/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/samuelgursky/davinci-resolve-mcp/resolve-audio"><img src="https://agentmods.dev/badge/instructions/samuelgursky/davinci-resolve-mcp/resolve-audio.svg" alt="Reviewed on agentmods" width="80" 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.00306 | $0.00306 |
| Opus 5 | $0.00153 | $0.00153 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
davinci-resolve-mcp resolve-audio.instructions.md 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- davinci-resolve-mcp resolve-audio.instructions.md — 100% identical, 2 lines differ
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. Portable skill: resolve-audio in .agents/skills/. 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.
- 7d ago Changed · +6 tokens per session d6dcfe1cf1bf
- 10d ago First seen · 15 lines · 300 tokens per session scan A b64fefd97178
davinci-resolve-mcp resolve-audio.instructions.md is an instructions file published in the GitHub repository samuelgursky/davinci-resolve-mcp (2,568 stars, last pushed today), licensed MIT. It adds 306 tokens to every session, about $0.0015 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-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.