Borrowing it
Nothing to install: this file belongs to Mandrilsquad1441/codex-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/Mandrilsquad1441/codex-davinci-resolve-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/Mandrilsquad1441/codex-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/mandrilsquad1441/codex-davinci-resolve-mcp/agents-md)<a href="https://agentmods.dev/instructions/mandrilsquad1441/codex-davinci-resolve-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/mandrilsquad1441/codex-davinci-resolve-mcp/agents-md.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.1 | $0.00432 | $0.00432 |
| Opus 5 | $0.00216 | $0.00216 |
| Sonnet 5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
codex-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 5d 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.
What it actually says
Codex DaVinci Resolve MCP repository guidance
This repository contains a local MCP server and an authenticated loopback bridge for DaVinci Resolve.
Required verification
Run these commands from the repository root with Python 3.11:
uv sync --all-extras --frozenPYTHONPATH=src .venv/bin/ruff format --check .PYTHONPATH=src .venv/bin/ruff check .PYTHONPATH=src .venv/bin/mypy src scripts/live_e2e.pyPYTHONPATH=src .venv/bin/pytestPYTHONPATH=src .venv/bin/python scripts/contract_check.pyuv builduv export --frozen --no-dev --no-hashes --no-emit-project --format requirements.txt | uvx pip-audit --requirement /dev/stdin --progress-spinner off --strict
For live testing, never use an existing user project. Start from a saved empty Codex MCP Bridge Bootstrap ... project. Use a uniquely named Codex MCP E2E ... project and outputs under ~/Movies/CodexResolveMCP/test-output/. The live path must prove a non-overwriting DRP backup, a versioned timeline revision, production preflight, delivery QC, and independent ffprobe validation. Destructive operations require a fresh, scoped confirmation token. Keep the Resolve bridge bound to 127.0.0.1; never enable network scripting.
Runtime constraints
- Resolve 21's Python loader works with the installed Python 3.11. Do not switch the connector to the system Python 3.13.
- Nothing except MCP protocol messages may be written to stdout by the server.
- Never add a generic
eval, raw Python/Lua execution tool, unrestricted filesystem tool, or arbitrary Resolve-method dispatcher. - Preserve the direct Studio transport and the Lite-compatible in-application bridge.
- Preserve signed protocol authentication; never send the shared bridge token on the socket or remove replay protection.
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.
- 5d ago First seen · 27 lines · 432 tokens per session scan A f43458e1eead
codex-davinci-resolve-mcp AGENTS.md is an instructions file published in the GitHub repository Mandrilsquad1441/codex-davinci-resolve-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 432 tokens to every session, about $0.0022 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-31.
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).
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 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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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.