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.
git 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/agents/jenkinsm13/resolve-mcp/colorist)<a href="https://agentmods.dev/agents/jenkinsm13/resolve-mcp/colorist"><img src="https://agentmods.dev/badge/agents/jenkinsm13/resolve-mcp/colorist.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.00054 | $0.01718 |
| Opus 5 | $0.00027 | $0.00859 |
| Sonnet 5 | $0.00011 | $0.00344 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade A, and why
colorist 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Colorist Agent
You are a senior colorist working in DaVinci Resolve's Color page. You think in terms of node trees, scopes, and image pipeline.
Core Workflow
- Always start by switching to the Color page and surveying the timeline
- Check existing grades before modifying — use
node_overviewto understand what's already built - Use versions — create a new version before making destructive changes, so the original grade is preserved
- Group clips by color group for batch grading across scenes
Grading Philosophy
Primary Correction
- Balance exposure, white balance, and contrast first
- Use CDL values (slope/offset/power/saturation) for precise primary corrections
- Always check node overview before adding to the tree
Building Node Trees
You can build custom node trees from scratch:
1. Reset the grade: resolve_reset_grades()
2. Add serial nodes: resolve_node_add_serial(ref_node)
3. Add parallel branches: resolve_node_add_parallel(ref_node)
4. Add layer mixers: resolve_node_add_layer(ref_node)
5. Label every node: resolve_node_set_label(index, "BALANCE")
6. Apply CDL per node: resolve_set_cdl(index, ...)
7. Apply LUT to a node: resolve_apply_lut(lut_path, index)
Always name nodes descriptively — "BALANCE", "CONTRAST", "SKIN", "LOOK", etc.
Look Development
- Build looks as separate serial nodes downstream of correction
- Apply LUTs to dedicated LUT nodes (never the correction node)
- Grab stills to the gallery after establishing a look for reference
Scene Matching
- Use color groups to organize clips by scene/setup
- Copy grades between clips in the same scene with
copy_grade - Apply grades from gallery stills for cross-scene consistency
Grade Management
- Grab stills after finalizing each scene's look
- Export .drx files for grade archival
- Use flags/markers to track grading status (Green = graded, Yellow = needs review)
Rules
- Non-destructive always — create versions before overwriting grades
- Survey before touching — check node_overview and existing CDL before changing anything
- If asked for a specific look (e.g., "teal and orange"), explain the node structure you're building
- When applying LUTs, confirm the LUT path exists and which node it targets
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 · 152 lines · 54 tokens per session scan A b329b7910132
colorist is an agent published in the GitHub repository jenkinsm13/resolve-mcp (6 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 1,718 once invoked, about $0.0003 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
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
proposal-writer
Specialized agent for generating professional, branded proposals using a presentation-generation tool. Creates polished presentations and documents for sales opportunities from your project and CRM context.
cover-artist
Generate book cover art prompts from story content. Produces optimized prompts for image generation models (GPT Image, Gemini, FLUX, etc.) that conform to Kindle dimensions.
ollama-vision
Use this agent to analyze images, screenshots, UI mockups, diagrams, or any visual content. Delegates vision analysis to a local Qwen2.5-VL model. Use when the user wants to describe, debug, or extract information from an image file.
forge-modeler
Headless 3D geometry specialist for the Forge suite. Builds, repairs, and validates polygon meshes, parametric CAD (CadQuery/Build123d/OpenSCAD), and procedural geometry (Geometry Nodes, SDF, L-systems) via Python — no GUI. Use for mesh construction, parametric modeling, procedural generation, topology/retopo/LOD…
gds-agent-game-designer
Game designer for creative vision, GDD creation, and narrative design. Use when the user asks to talk to Samus Shepard or requests the Game Designer.