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 skills/beeswaxpat/ffmpeg-render-pro/ffmpeg-render-pipelinenpx skills add beeswaxpat/ffmpeg-render-pro --skill ffmpeg-render-pipelinegit clone --depth 1 https://github.com/beeswaxpat/ffmpeg-render-proWrote 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/skills/beeswaxpat/ffmpeg-render-pro/ffmpeg-render-pipeline)<a href="https://agentmods.dev/skills/beeswaxpat/ffmpeg-render-pro/ffmpeg-render-pipeline"><img src="https://agentmods.dev/badge/skills/beeswaxpat/ffmpeg-render-pro/ffmpeg-render-pipeline.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.00055 | $0.03651 |
| Opus 5 | $0.00028 | $0.01826 |
| Sonnet 5 | $0.00011 | $0.00730 |
| Haiku 4.5 | $0.00006 | $0.00365 |
Grade A, and why
ffmpeg-render-pipeline 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 today.
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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ffmpeg Render Pipeline - Complete Reference
You are an expert video/audio render engineer. This skill covers the ffmpeg-render-pro toolkit - a parallel rendering system optimized for YouTube Shorts and long-form videos.
Toolkit location: The user may have ffmpeg-render-pro installed globally (npm install -g ffmpeg-render-pro provides the ffmpeg-render-pro CLI) or as a local dependency. Check with ffmpeg-render-pro version or node -e "require('ffmpeg-render-pro')". In a repo checkout, node bin/ffmpeg-render-pro.js is equivalent to the installed CLI.
Prerequisites
Before any render task, verify:
- Node.js >= 18 -
node --version - ffmpeg available -
ffmpeg -version. If ffmpeg is installed but not on PATH, setFFMPEG_RENDER_PRO_FFMPEGto its full path (a sibling ffprobe is auto-derived;FFMPEG_RENDER_PRO_FFPROBEoverrides it explicitly). Both are read at call time. - If ffmpeg is missing entirely, tell the user: "Install ffmpeg from https://ffmpeg.org/download.html and ensure it's on your PATH, or set FFMPEG_RENDER_PRO_FFMPEG to its full path."
Quick Start (for any render task)
The shortest path to a first render is three commands. Use it whenever the user has no worker script yet:
# 1. Prove the setup: 5s test render, dashboard opens
ffmpeg-render-pro benchmark
# 2. Write the starter worker (only renderFrame() needs editing; --force overwrites)
ffmpeg-render-pro init my-worker.js
# 3. Render it (output.mp4)
ffmpeg-render-pro render my-worker.js --duration=5
Without a global install, prefix each command with npx (npx ffmpeg-render-pro init). Over MCP the same path is get_worker_template (save starterSource to a file, edit renderFrame) then render_video.
# Check system capabilities
ffmpeg-render-pro info
# Render a YouTube Short shape (vertical, 60s) with the bundled test worker
ffmpeg-render-pro benchmark --width=1080 --height=1920 --fps=30 --duration=60
# Render with your own worker script
ffmpeg-render-pro render my-worker.js --duration=60 --output=video.mp4
# Force CPU or GPU encoding during detection
ffmpeg-render-pro detect-gpu --cpu
ffmpeg-render-pro detect-gpu --gpu
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.
- today Changed · +12 lines 7caa3f3777e3
- 5d ago First seen · 297 lines · 55 tokens per session scan A 21e611099368
ffmpeg-render-pipeline is a skill published in the GitHub repository beeswaxpat/ffmpeg-render-pro (3 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 3,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 skills, from other repositories
video-perception
Use when the user mentions a video file (.mp4, .mov, .avi, .mkv, .webm), a YouTube URL, asks to watch/analyze/review a video, or references video content in conversation.
general-video
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…