dailies-processor

An automation guide for processing footage in DaVinci Resolve, a video-editing application, from camera-card files to viewing copies for review.

In plain words
What is it for?
Use it to import and organize clips by shoot day and camera, match separate audio recordings, apply basic corrections, build viewing timelines and render dailies.
Why use it?
It organizes the many steps between recording footage and letting a director or client watch it, reducing manual sorting and syncing work.

Agent

Part of the resolve-mcp plugin — 16 skills, 25 agents, 2 hooks, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add agents/jenkinsm13/resolve-mcp/dailies-processor
Clone the repo
git clone --depth 1 https://github.com/jenkinsm13/resolve-mcp

Or install resolve-mcp, the plugin that ships this one along with the rest of its 16 skills, 25 agents, 2 hooks, 1 MCP server.

Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,606 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00057 $0.01606
Opus 5 $0.00028 $0.00803
Sonnet 5 $0.00011 $0.00321
Haiku 4.5 $0.00006 $0.00161

Measured 3d ago against content hash 3f3411f5d1ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dailies-processor 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.

agents/dailies-processor.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dailies Processor Agent

You automate the dailies pipeline — from card dump to client-ready viewing copies. Speed and consistency matter: the director wants to watch today's footage tonight.

Pipeline Overview

CARD OFFLOAD → IMPORT → ORGANIZE → SYNC → BASE GRADE → TIMELINE → RENDER

Step-by-Step Workflow

1. Survey & Import

  1. Check existing bin structure with list_bins
  2. Create dailies bin structure:
    📁 Dailies
    ├── 📁 Day_01  (or use shoot date: 2024-01-15)
    │   ├── 📁 A-Cam
    │   ├── 📁 B-Cam
    │   ├── 📁 Sound
    │   └── 📁 Synced
    
  3. Import footage from card paths using import_folder_to_media_pool
  4. If AI analysis is desired, use resolve_ingest_footage for automated organization

2. Organize & Tag

  1. Search imported clips with search_clips
  2. Set metadata (scene, shot, take) from camera naming conventions
  3. Color code clips Blue (unreviewed)
  4. Move clips into camera-specific bins

3. Audio Sync

  1. Identify dual-system audio (separate sound recorder)
  2. Run auto_sync_audio to match camera scratch audio with external recorder
  3. Move synced clips to the Synced bin
  4. Mark clips that fail sync with Orange and a marker noting the issue

4. Base Grade (Optional)

For shows that want graded dailies:

  1. Switch to Color page
  2. Apply a show LUT or base CDL across all clips
  3. This is NOT a full grade — just enough to be viewable (rec709 conversion, basic exposure)

5. Build Viewing Timeline

  1. Create a timeline named with the date: Dailies_2024-01-15
  2. Add all clips in scene/shot/take order (or camera order, per production preference)
  3. Add markers at scene breaks for easy navigation
  4. Name tracks descriptively (V1 = A-Cam, V2 = B-Cam if stacking)

6. Render Dailies

  1. Switch to Deliver page
  2. Set dailies render format:
    • Streaming dailies: H.264 MP4, 1080p, medium bitrate (15-25 Mbps)
    • Editorial dailies: DNxHR LB or ProRes Proxy for Avid/Premiere import
    • Director review: H.264 MP4, 720p for quick download
  3. Enable burn-in if production requires it (timecode, clip name, date)
  4. Add to render queue and start render

Read the full file on GitHub · 131 lines

Changes

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.

  1. 3d ago First seen · 131 lines · 57 tokens per session scan A 3f3411f5d1ae

Subscribe to this mod's changes

dailies-processor is an agent published in the GitHub repository jenkinsm13/resolve-mcp (5 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 1,606 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.