What is resolve-delivery?

A set of instructions for preparing and checking files delivered from DaVinci Resolve, such as finished renders, texted and textless versions, and audio stems.

Preparing render jobs, validating settings, checking finished renders against specifications, building render manifests, verifying media ingest, expanding deliverables, and producing provenance or episode reports.

It checks render settings, media completeness, loudness, framing, and provenance while leaving final quality decisions to a human reviewer.

resolve-delivery — Cursor rule for Cursor by mrsuber

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.

Clone the repo

git clone --depth 1 https://github.com/mrsuber/davinci-resolve-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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/mrsuber/davinci-resolve-mcp/resolve-delivery.svg)](https://agentmods.dev/rules/mrsuber/davinci-resolve-mcp/resolve-delivery)

Your own site

<a href="https://agentmods.dev/rules/mrsuber/davinci-resolve-mcp/resolve-delivery"><img src="https://agentmods.dev/badge/rules/mrsuber/davinci-resolve-mcp/resolve-delivery.svg" alt="Measured on agentmods" height="20"></a>

Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 380 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00054	$0.00380
Opus 5	$0.00027	$0.00190
Sonnet 5	$0.00011	$0.00076
Haiku 4.5	$0.00005	$0.00038

Measured 6d ago against content hash de8efe2c471f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

resolve-delivery 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 6d 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.

Origin

This is a copy

100% identical to resolve-delivery — 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.

.cursor/rules/resolve-delivery.mdc · 16 lines

What it actually says

Resolve Delivery / Deliverable QC work. Apply when: preparing render jobs, validating render settings, QCing a finished render vs spec, building render manifests, expanding texted/textless/stems deliverables, verifying media ingest, or producing a provenance/episode report.

Two servers — compute offline, apply live:

Live (running Resolve, davinci-resolve): render (probe_render_matrix, validate_render_settings, safe_set_render_settings, prepare_render_job, safe_quick_export), render_presets
Offline (.drp/.drt/.drx + DB, no Resolve, davinci-resolve-advanced): deliverable (deliverable_qc, loudness_qc, reframe_blanking_check, conform_completeness, render_manifest, expand_deliverable), media (ingest_verify, media_inventory, sync, rename_plan), provenance (grade_provenance, cdl_export, episode_report)
Key rule: Deliverable QC is report-only: gate=review, never auto-pass-clear — surface per-field verdicts to a human. QC tools refuse rather than fabricate. deliverable/media QC needs ffmpeg+ffprobe on PATH. Render probes touch only synthetic fixtures.

Depth: docs/kernels/render-deliver-kernel.md. On-demand in any MCP client: the /delivery_workflow slash prompt. Claude Code skill: resolve-delivery. Never modify/transcode/derive source media (AGENTS.md).

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.

6d ago First seen · 16 lines · 54 tokens per session scan A de8efe2c471f

Subscribe to this mod's changes

resolve-delivery is a cursor rule published in the GitHub repository mrsuber/davinci-resolve-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 380 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to resolve-delivery, differing in 2 lines, and is treated as a copy.

Creative and media

resolve-delivery

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

What it actually says

What this file has done since we first saw it

Other cursor rules, from other repositories

080-creative-phase-metrics

livkiet-plugins-playai

ponytail

angular-20

dev-standard

cli-error-handling