stage-edit

stage-edit is a skill for Claude Code, Codex from Orkas-AI/Orkas. It costs 0 tokens per session (3,382 once invoked), scanned A, original, MIT.

A controlled workflow for editing video according to an approved edit decision list, the plan that specifies the cuts and other changes.

In plain words
What is it for?
Use it to manage video cuts, joins, captions, overlays, reframing, audio, localization, and bounded content-aware edits to user-supplied footage.
Why use it?
It keeps video edits traceable and prevents production steps from running against a changed or unsigned plan.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to manage video cuts, joins, captions, overlays, reframing, audio, localization, and bounded content-aware edits to user-supplied footage.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orkas-ai/orkas/stage-edit
About the project

Orkas is a desktop application for commanding a team of AI agents through one chat, with a commander model assigning work to specialist agents in parallel or in sequence. People use it to coordinate research, writing, presentations, and software tasks while keeping files on their computer. The catalogue includes skills for extending the agents available to Orkas.

Orkas-AI/Orkas · 1,808 stars · on GitHub · orkas.ai

Install

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.

Any agent
npx skills add Orkas-AI/Orkas --skill stage-edit
Clone the repo
git clone --depth 1 https://github.com/Orkas-AI/Orkas

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for stage-edit

README.md
[![agentmods](https://agentmods.dev/badge/skills/orkas-ai/orkas/stage-edit.svg)](https://agentmods.dev/skills/orkas-ai/orkas/stage-edit)
Your own site
<a href="https://agentmods.dev/skills/orkas-ai/orkas/stage-edit"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/stage-edit.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,382 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.03382
Opus 5 $0.00000 $0.01691
Sonnet 5 $0.00000 $0.00676
Haiku 4.5 $0.00000 $0.00338

Measured 9d ago against content hash 6318ec4686f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

stage-edit 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 9d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/analyze_media.js, scripts/edit_video.js, scripts/lib/video_analyze_core.cjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

resources/builtin/marketplace/agents/79df9cc89f5f/skills/stage-edit/SKILL.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

stage-edit

For the VideoStudio EDIT line, the edit decision list lives in project/plan.json and gate-control owns its Gate B authorization transition. Start/resume execution with production.status; do not run trims, assembly, or localization against a changed or unsigned EDL. Runtime status/produced_path updates do not invalidate the signed creative plan, but changing cuts, copy, source allocation, or delivery settings does.

How to intelligently edit real user-supplied footage while keeping the source and every decision auditable. Deterministic operations still handle cuts, joins, captions, overlays, reframes, and audio. When the request changes pixels semantically—remove an object, alter a background, relight a shot, or make another content-aware local change—keep the EDIT route and execute only that bounded segment through signed video operation:"edit" after paid-generation approval.

Where the footage comes from. A user-uploaded clip arrives as a chat attachment marked model_readable="false" with a path (see the attachment list). That flag means "not vision input", NOT "unusable" — the file is exactly what these media scripts operate on. Copy it into the project's raw/ (or pass its attachment path directly as --input) before probing; never treat a model_readable="false" clip as something to skip.

Intelligent edit contract

Write project/plan.json::edit_strategy whenever VideoStudio decides what to change rather than merely executing user-supplied timecodes:

  • mode: deterministic for transcript/OCR/scene/silence/quality/vision-driven timeline decisions, semantic for AI pixel changes, or mixed when both are necessary. All four fields below are non-empty arrays of strings — one entry per item, never a single sentence. objectives is the one most often written as prose; the validator rejects a bare string with E_EDIT_STRATEGY_BOUNDARY.

  • objectives: the exact editorial or pixel-level changes requested, one per entry.

  • decision_signals: the provenance list of evidence actually used (timecode, transcript, ocr, scene, silence, quality, vision, semantic_model). Include each supplied or analyzed signal that supports the decision, not only the signal used to execute it.

  • preserve and may_change: non-overlapping boundaries. may_change must name every class of change the user authorized — omitting one silently narrows the plan's declared authority below what they asked for.

Read the full file on GitHub · 140 lines

Files

What ships with it

5 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.

Changes

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.

  1. 9d ago First seen · 140 lines · 0 tokens per session scan A 6318ec4686f1

Subscribe to this mod's changes

stage-edit is a skill published in the GitHub repository Orkas-AI/Orkas (1,808 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,382 tokens. 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-30.