Borrowing it
Nothing to install: this file belongs to flamexnreal/davinci-resolve-ai-bridge-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/flamexnreal/davinci-resolve-ai-bridge-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/flamexnreal/davinci-resolve-ai-bridge-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/flamexnreal/davinci-resolve-ai-bridge-mcp/agents-md)<a href="https://agentmods.dev/instructions/flamexnreal/davinci-resolve-ai-bridge-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/flamexnreal/davinci-resolve-ai-bridge-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/flamexnreal/davinci-resolve-ai-bridge-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/flamexnreal/davinci-resolve-ai-bridge-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.00777 | $0.00777 |
| Opus 5 | $0.00388 | $0.00388 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
davinci-resolve-ai-bridge-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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve AI Bridge Agent Instructions
Read README.md and skills/resolve-ai-editing/SKILL.md before changing the Python bridge or editing a Resolve project.
Architecture rules
bridge/operations.pyis the single implementation of every Resolve operation. Add new capability there, not in a transport. It must stay standard library only, and must never importmcporfusionscript.agent/ResolveConsole.pymay depend only on the standard library,bridge/operations.py,bridge/lifecycle.py, and Resolve's injected objects.- Never import Resolve from
bridge/server.py,bridge/client.py, ortools/. Onlybridge/direct.pyloads Resolve's native module, and only in a process that can afford to die. bridge/direct.pymust keep probing in a disposable subprocess before loading the native module in-process. A native module built for another Python can abort the process, and the MCP server has to survive that.- Fall back to the Console queue only before direct dispatch starts. After an unexpected dispatch failure, report an unknown outcome and never replay automatically.
- Keep Resolve API calls on the single operation worker. Heartbeat reporting must use cached Python data. Preserve deadline, session, per-client observed context and durable request checks.
- Stage and validate runtime/dependencies before activation; retain the previous runtime. Test installers in temporary directories, with no live client configuration changes.
- Never write normal output to stdout from
bridge/; stdio is reserved for MCP JSON-RPC. - Preserve token validation on every queue request.
- Preserve the non-blocking Console start and daemon operation worker. Only a confirmed separate
fuscriptmenu process may wait for that worker; never block Resolve's embedded interpreter. Menu-process Console output belongs on the main thread. - Keep the cross-process worker lock and authenticated, session-bound Stop signal. Only the separate menu child may exit when its Resolve parent dies.
- Use absolute installed paths in MCP configuration.
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.
- 3d ago Changed · +1 lines · +60 tokens per session f38311fde870
- 4d ago Changed · +14 lines · +269 tokens per session 279c90d2a481
- 11d ago First seen · 30 lines · 448 tokens per session scan A f70cdb0970ee
davinci-resolve-ai-bridge-mcp AGENTS.md is an instructions file published in the GitHub repository flamexnreal/davinci-resolve-ai-bridge-mcp (21 stars, last pushed 3d ago), licensed MIT. It adds 777 tokens to every session, about $0.0039 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).
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.
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.