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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/mrsuber/davinci-resolve-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/mrsuber/davinci-resolve-mcp/agents-md/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/agents-md"><img src="https://agentmods.dev/badge/instructions/mrsuber/davinci-resolve-mcp/agents-md.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.01985 | $0.01985 |
| Opus 5.5 | $0.00794 | $0.00794 |
| Sonnet 5.5 | $0.00397 | $0.00397 |
| Haiku 4.5 | $0.00198 | $0.00198 |
Grade A, and why
davinci-resolve-mcp AGENTS.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
94% identical to davinci-resolve-mcp AGENTS.md — 33 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DaVinci Resolve MCP Server — Agent Instructions
This is the canonical short operating brief for AI coding agents working in this repository. Keep it durable: do not duplicate version numbers, tool counts, kernel-action counts, release notes, or long reference tables here.
Non-Negotiable Source Media Safety
Never modify, transcode, convert, proxy, relink, replace, or create derivatives of source media unless the user explicitly asks for that exact operation.
Analysis workflows may read source media, but file outputs must go to sidecar
files, session scratch space, or the configured
davinci-resolve-mcp-analysis project root. Resolve-target analysis should run
visual analysis, transcription, metadata writeback, and Media Pool marker
writeback by default unless the user opts out; those writes are Resolve project
database changes, not source-media changes. Preserve the chain from camera
original to final delivery.
See docs/guides/media-analysis-guide.md for the full source-safe workflow.
Media Analysis Defaults Are Mandatory
Do not translate source-safe into underpowered, read-only, no-writeback analysis.
When the user asks to analyze Resolve media, run the requested analysis directly
with visual analysis, transcription, persisted artifacts, metadata writeback, and
Media Pool marker writeback enabled by default. Do not add
include_visuals=false, include_transcription=false,
publish_metadata=false, timed_markers=no, session_only=true, or
dry_run=true unless the user explicitly asks for that opt-out, the target is a
raw file path that cannot receive Resolve project writeback. Vision uses
host_chat_paths by default — analyze actions return a deferred payload with
absolute frame_paths and a JSON schema; the host chat must read those frames
as local images, produce JSON per the schema, and call
media_analysis(action="commit_vision", params={clip_id, visual, vision_token})
to merge the result and trigger metadata + Media Pool clip-marker writeback.
Not completing commit_vision leaves the analysis in
pending_host_vision_analysis — that is a failure mode, not a success. Users
must explicitly opt out with include_visuals=false for a technical-only run.
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 · 135 lines · 1,985 tokens per session scan A 7d0e4657c01f
davinci-resolve-mcp AGENTS.md is an instructions file published in the GitHub repository mrsuber/davinci-resolve-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,985 tokens to every session, about $0.0079 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to davinci-resolve-mcp AGENTS.md, differing in 33 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.