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/cut-segmentnpx skills add danielrosehill/Claude-Video-Editor-Plugin --skill cut-segmentgit 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/cut-segment)<a href="https://agentmods.dev/skills/danielrosehill/claude-video-editor-plugin/cut-segment"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-video-editor-plugin/cut-segment.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.00096 | $0.01213 |
| Opus 5 | $0.00048 | $0.00607 |
| Sonnet 5 | $0.00019 | $0.00243 |
| Haiku 4.5 | $0.00010 | $0.00121 |
Grade A, and why
cut-segment 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 6d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut Segment
Extract precise time ranges from a video. Replaces the legacy cut-video-segment command.
Procedure
1. Inputs
| Field | Default |
|---|---|
| Source | required |
| Segments | required: one or more start..end ranges (e.g. 00:01:30..00:03:45) or a JSON array [{start, end, label?}, ...] |
| Output dir | default: same dir as source (or <project>/exports/ when run inside a project) |
| Mode | copy (lossless, stream-copy) — precise (re-encode for frame-accurate cuts) |
| Stitch | no (one file per segment) — yes (concatenate all segments into a single output) |
2. Validate ranges
SRC="$(realpath "$INPUT")"
DUR=$(ffprobe -v error -show_entries format=duration -of default=nw=1:nk=1 "$SRC")
to_seconds() {
awk -F: '{
n = NF
if (n == 3) print $1*3600 + $2*60 + $3
else if (n == 2) print $1*60 + $2
else print $1
}' <<<"$1"
}
For each segment: convert start/end to seconds; reject if start >= end, if start < 0, or if end > DUR. Report which segments were rejected and abort.
3. Mode: copy (default)
Stream-copy each segment. Fast, lossless, but cuts land on the nearest keyframe (typically within 1–2s of the requested mark).
i=0
for seg in "${SEGMENTS[@]}"; do
read s e <<<"$seg"
OUT="$OUTDIR/$(basename "${SRC%.*}")_seg_$(printf '%02d' $i)${EXT}"
ffmpeg -y -ss "$s" -to "$e" -i "$SRC" -c copy -avoid_negative_ts make_zero "$OUT"
i=$((i+1))
done
-ss before -i enables fast seek; combined with -c copy this is the lossless path.
4. Mode: precise
Frame-accurate cuts via re-encode. -ss goes after -i to force decode-side seek.
ffmpeg -y -i "$SRC" -ss "$s" -to "$e" \
-c:v libx264 -crf 18 -preset medium \
-c:a aac -b:a 192k \
"$OUT"
If a render profile name was supplied (from render-profiles.json), build the encoder args from that profile instead.
5. Stitch (optional)
If STITCH=yes:
LIST=$(mktemp)
for f in "${SEGMENT_OUTPUTS[@]}"; do printf "file '%s'\n" "$f" >> "$LIST"; done
ffmpeg -y -f concat -safe 0 -i "$LIST" -c copy "$OUTDIR/$(basename "${SRC%.*}")_stitched${EXT}"
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.
- 6d ago First seen · 104 lines · 96 tokens per session scan A 8a1cbab4aefd
cut-segment 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,213 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…