One key, every video model
Wiring a hosted video agent into your coding agent — it plans the shots, picks the model per shot, and returns a finished MP4
One install and one API key put a hosted video agent behind your coding agent: you describe a video in conversation, it writes the script, picks a model per shot, generates the clips, adds music, narration and subtitles, and hands back a single finished MP4. The skills are free and MIT; the generations cost credits, and nothing paid runs without you approving an estimate first.
Most video skills wrap one model and hand back a raw clip. This one returns a finished, multi-shot video — script, shot sequencing, per-shot model selection, music, narration, subtitles and transitions, assembled. You give it a brief in conversation and take delivery of an MP4. The trade is that you are not choosing the models for the automated path; a hosted backend is. Separate studio skills exist for when you do want that control.
Four kinds of skill, two levels of control
The repository does advertise 10+ video models, and its own README carries that badge. But it names only four of them for the auto-selecting agent — Seedance 2, Kling 3.0, HappyHorse and Grok — with the rest given as “and others”. The full list is not published. What you can actually name and pick by hand is 7 in the video studio and 8 in the image studio. Both figures were confirmed against the README today. Nothing dishonest here, but “10+” is a backend claim you cannot audit, while 7 and 8 are lists you can.
What you need — and what you do not
One key covers every model the automated agent uses. No per-model API keys, no FFmpeg, no Python.
Install it
The global flag installs to a shared skills folder and symlinks it in, so every project sees it. Drop the flag to install into the current project only. Add another --skill argument for each studio you want.
Give it your key
The key lives in this file and never in a prompt. The base URL line is optional, and must be exactly the service’s own address if you set it at all.
Run the doctor, then a read-only test
The doctor checks the config, the required command-line tools, network reachability and whether the key actually works. Neither call spends credits — which is the point of doing them first.
The seven you can pick by hand
These are the video-studio models. All run through a hosted proxy, so none of them needs its own key.
The other two studios
Driving a studio directly
Install the studio skill first. This is the escape hatch for when you want one specific clip rather than a finished film.
What actually happens on a run
You only talk; the agent runs the scripts. Note where the gate sits — the estimate comes before any generation, and approval is a separate explicit call.
The repository’s own figures: around eight minutes for a fifteen-second, three-shot ad, and around twenty minutes for a sixty-second brand video. Your agent hands you the project link so you can watch progress there rather than sitting in the terminal. Budget the wait — this is not an interactive loop.
The master prompt
Written to match how the thing actually works: the backend selects models, so you ask for the plan and the estimate rather than trying to dictate models. The line that matters most is the one forbidding it to approve on your behalf.
Three to try
Illustrative only — no brand affiliation implied. Each one keeps the estimate gate in place.
Where the output lands
The automated agent delivers a single rendered MP4 — if you wanted the loose clips to edit yourself, that is the studio skills, which are the exact opposite shape. Worth knowing before you plan an edit around it. Downloads are watermark-free by default, but that depends on an active subscription; without one, ask for the watermarked variant explicitly.
What costs money
The distinction that matters: the skills are free and open source, the generations are not.
Troubleshooting
Quick start
Checked against the repository on 18 September 2026 rather than taken on trust. The licence is MIT and the version file still reads 0.3.12 — the same release the source guide pinned in August, so its commands and paths are current despite ongoing repository activity. The install command matches the README exactly. The model counts were verified too: the README does carry a 10+ badge while naming only four models for the automated path, and the studio lists really are 7 video and 8 image models. A referral code that appeared in the source’s credits section is not reproduced here, and neither is the author’s byline or follow prompt.