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/dailies-processorgit 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.00057 | $0.01606 |
| Opus 5 | $0.00028 | $0.00803 |
| Sonnet 5 | $0.00011 | $0.00321 |
| Haiku 4.5 | $0.00006 | $0.00161 |
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.
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
- Check existing bin structure with
list_bins - Create dailies bin structure:
📁 Dailies ├── 📁 Day_01 (or use shoot date: 2024-01-15) │ ├── 📁 A-Cam │ ├── 📁 B-Cam │ ├── 📁 Sound │ └── 📁 Synced - Import footage from card paths using
import_folder_to_media_pool - If AI analysis is desired, use
resolve_ingest_footagefor automated organization
2. Organize & Tag
- Search imported clips with
search_clips - Set metadata (scene, shot, take) from camera naming conventions
- Color code clips Blue (unreviewed)
- Move clips into camera-specific bins
3. Audio Sync
- Identify dual-system audio (separate sound recorder)
- Run
auto_sync_audioto match camera scratch audio with external recorder - Move synced clips to the
Syncedbin - Mark clips that fail sync with Orange and a marker noting the issue
4. Base Grade (Optional)
For shows that want graded dailies:
- Switch to Color page
- Apply a show LUT or base CDL across all clips
- This is NOT a full grade — just enough to be viewable (rec709 conversion, basic exposure)
5. Build Viewing Timeline
- Create a timeline named with the date:
Dailies_2024-01-15 - Add all clips in scene/shot/take order (or camera order, per production preference)
- Add markers at scene breaks for easy navigation
- Name tracks descriptively (V1 = A-Cam, V2 = B-Cam if stacking)
6. Render Dailies
- Switch to Deliver page
- 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
- Enable burn-in if production requires it (timecode, clip name, date)
- Add to render queue and start render
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 · 131 lines · 57 tokens per session scan A 3f3411f5d1ae
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.
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.