stage-plan

stage-plan is a skill for Claude Code, Codex from Orkas-AI/Orkas. It costs 2 tokens per session (6,170 once invoked), scanned A, original, MIT.

A skill that turns source media and a desired video result into a structured editing plan. The plan records choices about footage, images, generated material, timing, and composition in a file called project/plan.json.

In plain words
What is it for?
Use it to organize a video from uploaded clips and reference images or videos, including scene selection, silence, text recognition, quality checks, transcription, generation, and final assembly.
Why use it?
It gives an editing project one inspectable set of decisions instead of leaving choices scattered across tools or notes. It also requires source clips to be examined before the plan is written.

Skill for Claude CodeCodex

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

Good fit Use it to organize a video from uploaded clips and reference images or videos, including scene selection, silence, text recognition, quality checks, transcription, generation, and final assembly.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orkas-ai/orkas/stage-plan
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,848 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-plan
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-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/orkas-ai/orkas/stage-plan/github.svg)](https://agentmods.dev/skills/orkas-ai/orkas/stage-plan)
Your own site
<a href="https://agentmods.dev/skills/orkas-ai/orkas/stage-plan"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/stage-plan/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.

agentmods 80×15 button for stage-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/orkas-ai/orkas/stage-plan"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/stage-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,170 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.00002 $0.06170
Opus 5 $0.00001 $0.03085
Sonnet 5 $0.00000 $0.01234
Haiku 4.5 $0.00000 $0.00617

Measured 10d ago against content hash 391cf257f740, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

stage-plan 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.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/lib/video_decide_core.cjs, scripts/lib/video_edl_core.cjs, scripts/video_plan.js), 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-plan/SKILL.md · 208 lines

How it starts

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

stage-plan

How to turn "here is my material + here's the video I want" into a single, inspectable plan that spans reference images, reference videos, deterministic editing, semantic editing, generation, and composition. The output is project/plan.json — a cross-modal Edit Decision List (EDL) — which the assembler walks. Host-neutral: ingest evidence comes from stage-edit skill scripts (probe / silence / ocr / scenes / quality / extract_frame) plus video_studio transcription; this skill provides the plan validator, and line producers execute the signed decisions.

Where the material comes from. User-uploaded clips arrive as chat attachments marked model_readable="false" with a path (see the attachment list). That flag means "not vision input", NOT "unusable" — it is source material to ingest with the scripts below. Copy each into raw/ (or pass its attachment path as --input) before probing; never skip a model_readable="false" clip or plan around material you have not actually ingested.

How to call ingest scripts

Use stage-edit scripts for factual ingest before writing the plan, except transcription, which runs through the required built-in video_studio tool.

"$ORKAS_NODE" "$ORKAS_PC_DIR/bin/run-skill.cjs" stage-edit edit_video -- --op probe --input raw/clip.mp4
"$ORKAS_NODE" "$ORKAS_PC_DIR/bin/run-skill.cjs" stage-edit analyze_media -- --op ocr --input raw/screen-recording.mp4
"$ORKAS_NODE" "$ORKAS_PC_DIR/bin/run-skill.cjs" stage-edit edit_video -- --op extract_frame --input raw/clip.mp4 --start 3 --output project/frames/clip-3s.png

Call transcription directly as:

{"op":"speech.transcribe","input_path":"raw/clip.mp4","transcript_path":"project/transcripts/clip.json","timestamps":"word"}

These script/tool calls return JSON. Their output is the evidence for project/ingest.json.

How to call the plan validator

Use the skill script, not a deprecated direct video_plan tool:

"$ORKAS_NODE" "$ORKAS_PC_DIR/bin/run-skill.cjs" stage-plan video_plan -- --op validate --plan project/plan.json
"$ORKAS_NODE" "$ORKAS_PC_DIR/bin/run-skill.cjs" stage-plan video_plan -- --op promise_check --plan project/plan.json
"$ORKAS_NODE" "$ORKAS_PC_DIR/bin/run-skill.cjs" stage-plan video_plan -- --op summarize --plan project/plan.json

Read the full file on GitHub · 208 lines

Files

What ships with it

3 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. 10d ago First seen · 208 lines · 2 tokens per session scan A 391cf257f740

Subscribe to this mod's changes

stage-plan is a skill published in the GitHub repository Orkas-AI/Orkas (1,848 stars, last pushed today), licensed MIT. It adds 2 tokens to every session and 6,170 once invoked, about $0.0000 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-30.