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 skills add blitzreels/agent-skills --skill blitzreels-editinggit clone --depth 1 https://github.com/blitzreels/agent-skillsWrote 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/blitzreels/agent-skills/blitzreels-editing)<a href="https://agentmods.dev/skills/blitzreels/agent-skills/blitzreels-editing"><img src="https://agentmods.dev/badge/skills/blitzreels/agent-skills/blitzreels-editing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/blitzreels/agent-skills/blitzreels-editing"><img src="https://agentmods.dev/badge/skills/blitzreels/agent-skills/blitzreels-editing.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00524 |
| Opus 5 | $0.00015 | $0.00262 |
| Sonnet 5 | $0.00006 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
blitzreels-editing 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 10d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BlitzReels Editing
Treat CLI and REST as execution branches of the same project edit. Use the installed CLI for direct workspace operation and REST for integrations or explicit API work.
Workflow
- Choose the surface.
- CLI: confirm
command -v blitzreels, then inspect the exact command withagent-context --command. - REST: load the capability index, then inspect only the required OpenAPI operations.
- If the CLI is absent, continue through REST when the public contract supports the edit.
- CLI: confirm
- Read the project and bounded timeline context before selecting IDs. Load caption words or media only for the affected interval.
- Choose the highest-level operation that owns the full change.
- Speech removal: timeline cut with caption ripple.
- Caption correction: word text, merge, split, delete, retime, or block patch.
- Visual placement: media insertion or transform using placement presets first.
- Editable text: content items.
- Preview risky writes with dry run or a plan. Review destructive output before passing a confirmation flag.
- Mutate with an idempotency key when the contract accepts one.
- Re-read the affected state and render frames at every changed interval.
- Start an export only after visual verification and approval for paid rendering. Poll it to terminal success and verify that the output is retrievable.
CLI discovery
blitzreels agent-context --command "timeline cut" --json
blitzreels agent-context --command "captions words list" --json
blitzreels agent-context --command "media attach" --json
blitzreels agent-context --command "project snapshots" --json
Use project inspect --mode full only when deep word-level metadata is required.
Recovery
- On a stale ID or conflict, discard the pending edit, refresh context, and select the target again.
- On partial failure, account for every item and retry only failed items after verification.
- When an API call may have reached the server, read current state before retrying.
- After attaching transcribed media, refresh the timeline before adding layers because captions can overlap.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 53 lines · 31 tokens per session scan A d899067f8c3f
blitzreels-editing is a skill published in the GitHub repository blitzreels/agent-skills (3 stars, last pushed 10d ago), licensed MIT. It adds 31 tokens to every session and 524 once invoked, about $0.0002 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
authoring-video-templates
Use when creating or editing a video template JSON (the template descriptor), adding or changing sections/filters/maps/variables/transitions/looks/motion/audio/layers, or debugging template validation errors in ffmpeg-video-composer.
core-architecture-patterns
Use when adding a segment type, platform adapter, editor manager, core service, or descriptor effect (look/grade/motion/section-audio field) in packages/ffmpeg-video-composer, or when wiring new dependencies into the tsyringe container.
ondevice-ffmpeg-engine
Use when building, modifying, or consuming the on-device FFmpeg engine — the Rust crate packages/ffmpeg-engine, the leclap-ffmpeg Expo native module, the run/probe/version/cancel API, the uniffi bindings, build-engine.sh, or the FFmpeg-from-source toolchain in scripts/ffmpeg.
cross-platform-ffmpeg
Use when working with FFmpeg across Node/Static/WASM, the PlatformBridge, the FFmpeg detection/fallback chain, or browser/React Native runtime constraints in ffmpeg-video-composer.
kling-studio
Full-featured Kling 3.0 Omni video generation skill. Covers text-to-video, image-to-video, video editing (base mode), video reference (feature mode), multi-shot generation, and audio-synced video. Includes validated API constraint rules and prompt engineering guide.
seedance-prompt
This skill should be used when the user asks to write, improve, translate, compress, or debug a Seedance 2.0 video prompt; mentions T2V, I2V, V2V, R2V, camera direction, prompt quality, or provides reference assets for a production-ready prompt.