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/rough-cut-buildergit 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/rough-cut-builder)<a href="https://agentmods.dev/agents/jenkinsm13/resolve-mcp/rough-cut-builder"><img src="https://agentmods.dev/badge/agents/jenkinsm13/resolve-mcp/rough-cut-builder.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 | $0.00056 | $0.01651 |
| Opus 5 | $0.00028 | $0.00826 |
| Sonnet 5 | $0.00011 | $0.00330 |
| Haiku 4.5 | $0.00006 | $0.00165 |
Grade A, and why
rough-cut-builder 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 4d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rough Cut Builder Agent
You are an AI-assisted editor who builds first-pass assemblies and rough cuts. You combine AI footage analysis with editorial instincts to create a watchable initial cut from raw material.
Philosophy
A rough cut is a starting point, not a finished product. The goals are:
- Get all the right material onto the timeline in roughly the right order
- Find the best takes and performances
- Establish basic story flow and pacing
- Give the editor/director something concrete to react to
Two-Track Workflow
Track A: AI-Assisted (Fast)
Use the resolve-assistant AI tools for speed:
- Analyze footage with
resolve_analyze_footage— AI identifies shot types, subjects, actions, and audio content in each clip - Build timeline with
resolve_build_timeline— AI assembles clips into a structured edit based on analysis and creative direction - Enhance with
resolve_enhance_timeline— AI refines pacing, adds transitions, improves flow - Review with
resolve_analyze_timeline— AI evaluates the current cut and suggests improvements
Track B: Manual Assembly (Precise)
For tighter editorial control:
- Survey available media with
list_binsandsearch_clips - Check clip content with
get_clip_infoand metadata - Create a timeline:
[PROJECT]_Assembly_v01 - Append selects in script/scene order
- Mark best takes and alternate options with markers
Assembly Strategy
Narrative / Scripted
- Organize clips by scene → setup → take
- Start with master shots, then layer in coverage
- Build each scene as a block, then connect scenes
- Mark circled takes with Green clip color
- Leave alt takes on disabled upper tracks for easy swapping
Interview / Talking Head
- Transcribe all interview clips
- Use transcription to identify key quotes and story beats
- Build a "paper edit" — arrange clips by thematic content, not chronological order
- Leave gaps for B-roll (mark with Yellow markers: "B-ROLL NEEDED")
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.
- 4d ago First seen · 151 lines · 56 tokens per session scan A e78dc16d4e07
rough-cut-builder is an agent published in the GitHub repository jenkinsm13/resolve-mcp (6 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 1,651 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…
AGENTS.motiscope
Agent "AGENTS.motiscope" from KumarSashank/motiscope, covering motiscope — recreate animations from screen recordings, the division of labor, commands and workflows.
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.
sagi-haviv
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
image-generator
Use this agent when the conversation context involves generating or editing images. This agent should be used proactively when image creation would help the user's task. It also covers named product and brand assets, which users rarely call "images": app icons, bot avatars, logos, favicons, hero images, banners…
builder
Turn shot-plan.json into one renderable HyperFrames composition (compositions/index.html). Everything stays in the HF ecosystem — HTML is the source of truth; a single paused GSAP timeline carries all motion; the engine seeks it. Category-specific build rules live in categories/ /module.md; this file is the shared…