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 cjhyy/codeshell --skill video-editorgit clone --depth 1 https://github.com/cjhyy/codeshellWrote 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/cjhyy/codeshell/video-editor)<a href="https://agentmods.dev/skills/cjhyy/codeshell/video-editor"><img src="https://agentmods.dev/badge/skills/cjhyy/codeshell/video-editor/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/cjhyy/codeshell/video-editor"><img src="https://agentmods.dev/badge/skills/cjhyy/codeshell/video-editor.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.00068 | $0.00956 |
| Opus 5.5 | $0.00027 | $0.00382 |
| Sonnet 5.5 | $0.00014 | $0.00191 |
| Haiku 4.5 | $0.00007 | $0.00096 |
Grade A, and why
video-editor 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Video Editor
Use the bundled deterministic editor instead of improvising shell-escaped
FFmpeg commands. The editor passes arguments directly to ffmpeg/ffprobe
without a shell and supports a reviewable JSON edit plan.
Editor path:
${CODESHELL_SKILL_DIR}/scripts/video-editor.mjs
Safety contract
- Confirm that the user has the right to edit the media.
- Never overwrite an existing output unless the user explicitly approves it.
- Inspect first, then write a plan, then run
--dry-run, then render. - Keep the source file unchanged. Write outputs to a new path.
- Do not install FFmpeg or other system packages without asking.
- For long renders, use background Bash and wait for the completion wake-up instead of polling repeatedly.
- Treat subtitle files and external audio as untrusted paths. Pass them only through the plan; do not interpolate them into hand-written shell commands.
Workflow
- Check tools:
node "${CODESHELL_SKILL_DIR}/scripts/video-editor.mjs" check
- Probe the source and report duration, resolution, codecs, frame rate, and whether audio exists:
node "${CODESHELL_SKILL_DIR}/scripts/video-editor.mjs" probe --input "/absolute/input.mp4"
-
Create
.code-shell/video-edits/<name>.json. Use absolute paths when the request spans multiple directories. Read${CODESHELL_SKILL_DIR}/references/plan-schema.mdfor the schema. -
Validate the exact command without writing:
node "${CODESHELL_SKILL_DIR}/scripts/video-editor.mjs" render \
--plan ".code-shell/video-edits/<name>.json" --dry-run
-
Summarize the edit decision: kept ranges, removed duration, output aspect, subtitle/audio changes, output path, and whether an existing file would be replaced. Resolve ambiguities with the user before rendering.
-
Render:
node "${CODESHELL_SKILL_DIR}/scripts/video-editor.mjs" render \
--plan ".code-shell/video-edits/<name>.json"
- Probe the output and report its path and media facts. If the user requests visual QA, extract representative frames through the same safe wrapper and inspect them:
What ships with it
2 files 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.
- 6d ago First seen · 107 lines · 68 tokens per session scan A 108291a675ba
video-editor is a skill published in the GitHub repository cjhyy/codeshell (65 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 956 once invoked, about $0.0003 per session on Opus 5.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-10-14.
Other skills, from other repositories
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…