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/danielrosehill/claude-video-editor-plugin/create-render-profilenpx skills add danielrosehill/Claude-Video-Editor-Plugin --skill create-render-profilegit clone --depth 1 https://github.com/danielrosehill/Claude-Video-Editor-PluginWrote 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/danielrosehill/claude-video-editor-plugin/create-render-profile)<a href="https://agentmods.dev/skills/danielrosehill/claude-video-editor-plugin/create-render-profile"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-video-editor-plugin/create-render-profile.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.00096 | $0.01358 |
| Opus 5 | $0.00048 | $0.00679 |
| Sonnet 5 | $0.00019 | $0.00272 |
| Haiku 4.5 | $0.00010 | $0.00136 |
Grade A, and why
create-render-profile 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 5d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Render Profile
Walks the user through building a render profile interactively, with a tight feedback loop: render a short test clip, inspect file size + bitrate, tune, repeat.
This is the antidote to "GPU-encoded but bloated". The goal is a profile the user trusts — saved by name, reused across jobs.
Procedure
1. Resolve the system profile
DATA_DIR="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/video-editing"
PROFILE_FILE="$DATA_DIR/system-profile.json"
PROFILES_FILE="$DATA_DIR/render-profiles.json"
test -f "$PROFILE_FILE" || { echo "No system profile — run profile-system first."; exit 1; }
Read preferred encoders and the VAAPI render node from system-profile.json.
2. Ask the user
| Field | Example | Default |
|---|---|---|
| Profile name | youtube-1080p |
required, slugify |
| Container | mp4 / mkv / mov | mp4 |
| Codec | h264 / hevc / av1 | hevc (best size/quality) |
| Resolution | 1920x1080 / 3840x2160 / source | source |
| Framerate | 30 / 60 / source | source |
| Quality target | "small file", "YouTube", "archival" | "YouTube" |
| Sample clip | path to a representative source file | required |
Map quality target → starting QP / bitrate (per encoder). Reasonable starting points:
- VAAPI HEVC:
-qp 23(YouTube),-qp 20(archival),-qp 28(small file) - VAAPI H.264:
-qp 22(YouTube),-qp 18(archival),-qp 27(small file) - libx264/libx265:
-crf 20/-crf 23/-crf 28
3. Build the ffmpeg command
For AMD VAAPI HEVC at 1080p:
ffmpeg -hide_banner -ss 0 -t 30 -i "<sample>" \
-vaapi_device "<render_node>" \
-vf 'format=nv12,hwupload,scale_vaapi=w=1920:h=1080' \
-c:v hevc_vaapi -qp <QP> \
-c:a aac -b:a 192k \
-movflags +faststart \
"<test_out>"
For software fallback (x265):
ffmpeg -hide_banner -ss 0 -t 30 -i "<sample>" \
-vf scale=1920:1080 \
-c:v libx265 -crf <CRF> -preset medium \
-c:a aac -b:a 192k \
-movflags +faststart \
"<test_out>"
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.
- 5d ago First seen · 127 lines · 96 tokens per session scan A 996eb865fe0e
create-render-profile is a skill published in the GitHub repository danielrosehill/Claude-Video-Editor-Plugin (5 stars, last pushed 4mo ago), licensed MIT. It adds 96 tokens to every session and 1,358 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…