Borrowing it
Nothing to install: this file belongs to jenkinsm13/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/jenkinsm13/resolve-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/jenkinsm13/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/jenkinsm13/resolve-mcp/claude-md)<a href="https://agentmods.dev/instructions/jenkinsm13/resolve-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/jenkinsm13/resolve-mcp/claude-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.02227 | $0.02227 |
| Opus 5 | $0.01113 | $0.01113 |
| Sonnet 5 | $0.00445 | $0.00445 |
| Haiku 4.5 | $0.00223 | $0.00223 |
Grade A, and why
resolve-mcp CLAUDE.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 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
resolve-mcp
MCP server exposing ~296 tools for the DaVinci Resolve scripting API (v20.3), plus AI bridge tools powered by Google Gemini.
Quick Start
pip install -e ".[dev]" # install package + ruff/pytest/pyright
cp .env.example .env # optional — only needed for AI bridge tools
resolve-mcp # run the MCP server (needs Resolve open)
pytest tests/ -v # run tests (no Resolve needed)
Architecture
- Package:
resolve_mcp/— all modules use relative imports (from .config import mcp) - Entry point:
resolve_mcp/__init__.py→main()→mcp.run() - Tool registration: Every tool module is imported in
__init__.py. The@mcp.tooldecorator on each function auto-registers it with the FastMCP server. - MCP resources:
resources.pyexposes read-onlyresolve://URIs (project, timelines, bins, render-queue, version)
Key Patterns
Adding a new tool
- Create or edit a
*_tools.pymodule - Import
from .config import mcpandfrom .resolve import get_resolve, _boilerplate - Decorate with
@mcp.tool - If the module is new, add
from . import my_new_toolsin__init__.py
Gotcha — cascading imports: 18 modules are loaded indirectly through import chains rather than __init__.py. For example, edit_tools.py imports clip_edit_tools, which imports clip_query_tools. If you add tools to one of these indirect modules, they'll register correctly without touching __init__.py — but only because the parent module already imports them. See tests/test_conventions.py::INDIRECT_IMPORT_MODULES for the full list.
Resolve connection
get_resolve()returns the Resolve scripting object (orNoneif not running)_boilerplate()returns(resolve, project, media_pool)— a 3-tuple, no timeline. Get timeline separately:project.GetCurrentTimeline()- All Resolve API calls go through the network scripting interface
Error handling
@safe_resolve_calldecorator inerrors.pywraps tools to catch exceptions and return MCP-friendly error strings — including your own bugs (NameError,KeyError, etc.), which become silent string returns instead of tracebacks- Custom exception classes:
ResolveNotRunning,ProjectNotOpen,TimelineNotFound,BinNotFound,ClipNotFound,ItemNotFound,StudioRequired
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 · 139 lines · 2,227 tokens per session scan A 54bb6f978e78
resolve-mcp CLAUDE.md is an instructions file published in the GitHub repository jenkinsm13/resolve-mcp (6 stars, last pushed 4mo ago), licensed MIT. It adds 2,227 tokens to every session, about $0.0111 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
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).
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.
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.