Borrowing it
Nothing to install: this file belongs to mrsuber/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/mrsuber/davinci-resolve-mcp/main/.github/instructions/resolve-delivery.instructions.mdgit 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/instructions/mrsuber/davinci-resolve-mcp/resolve-delivery)<a href="https://agentmods.dev/instructions/mrsuber/davinci-resolve-mcp/resolve-delivery"><img src="https://agentmods.dev/badge/instructions/mrsuber/davinci-resolve-mcp/resolve-delivery/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/mrsuber/davinci-resolve-mcp/resolve-delivery"><img src="https://agentmods.dev/badge/instructions/mrsuber/davinci-resolve-mcp/resolve-delivery.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.00323 | $0.00323 |
| Opus 5.5 | $0.00129 | $0.00129 |
| Sonnet 5.5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
davinci-resolve-mcp resolve-delivery.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 1mo 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 davinci-resolve-mcp resolve-delivery.instructions.md — 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 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).
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.
- 1mo ago First seen · 15 lines · 323 tokens per session scan A 79f8f7cfed46
davinci-resolve-mcp resolve-delivery.instructions.md is an instructions file published in the GitHub repository mrsuber/davinci-resolve-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 323 tokens to every session, about $0.0013 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to davinci-resolve-mcp resolve-delivery.instructions.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
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.