Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/jenkinsm13/resolve-mcp/api-coverage-checkergit clone --depth 1 https://github.com/jenkinsm13/resolve-mcpWhat 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 | $0.00036 | $0.00715 |
| Opus 5 | $0.00018 | $0.00358 |
| Sonnet 5 | $0.00007 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
api-coverage-checker 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Coverage Checker for resolve-mcp
You analyze the resolve-mcp tool set against the DaVinci Resolve scripting API documentation to find coverage gaps.
How to Check Coverage
Step 1: Inventory current tools
Read resolve_mcp/__init__.py to get the full module list and tool counts. Then read each module to catalog every @mcp.tool function.
Step 2: Map to Resolve API objects
The Resolve scripting API is organized by object:
| Resolve Object | Expected Module(s) |
|---|---|
Resolve |
project_tools, resolve_info_tools |
ProjectManager |
project_mgr_tools |
Project |
project_tools, project_misc_tools |
MediaStorage |
media_storage_tools |
MediaPool |
media_pool_tools, media_pool_edit_tools, media_pool_query_tools |
MediaPoolItem |
clip_metadata_tools, clip_query_tools, clip_edit_tools |
Folder (Bin) |
folder_tools |
Timeline |
timeline_mgmt_tools, timeline_query_tools, timeline_track_tools |
TimelineItem |
edit_tools, item_marker_tools, item_version_tools |
Gallery |
gallery_tools |
GalleryStill |
gallery_tools |
ColorNode |
node_tools, color_tools, color_grade_tools |
Fusion |
fusion_tools, fusion_node_tools |
Fairlight |
fairlight_tools, audio_mapping_tools |
Render |
render_tools, render_settings_tools, render_queue_tools |
Step 3: Find gaps
For each Resolve API object, check if all documented methods have a corresponding MCP tool. Report:
- Missing methods — API method exists but no tool wraps it
- Partial coverage — tool exists but doesn't expose all parameters
- Deprecated methods — tool wraps a method that's been deprecated
Step 4: Report
## API Coverage Report
### Summary
- Total tools: {N}
- API objects covered: {N}/{total}
- Estimated coverage: {percentage}%
### Missing Coverage
| Resolve Object | Missing Method | Priority |
|---------------|---------------|----------|
| {object} | {method} | High/Medium/Low |
### Partial Coverage
| Tool | Missing Parameters |
|------|-------------------|
| {tool_name} | {param1, param2} |
### Recommendations
1. {Highest priority gap to fill}
2. {Next priority}
3. {etc.}
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 First seen · 80 lines · 36 tokens per session scan A 7e620e9669a3
api-coverage-checker is an agent published in the GitHub repository jenkinsm13/resolve-mcp (5 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 715 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.