Two kits. One license.
Both kits install into the same AI coding tool you already use, and both render on your machine — nothing about your project is uploaded anywhere. Film Kit and Reel Kit are two different workflows for two different kinds of video: one is led by a story, the other by a beat.
One key covers both. Install one or both — npx bountex-motion install film and npx bountex-motion install reel. install film is what you get when you leave the argument out.
Kit 1 of 2 · v1.1.0
Film Kit
A creative director and production orchestrator for product and brand films: adaptive interview, creative direction, production prompt, storyboard, deterministic build, and an independent critic loop.
Trigger
$/bountex-motionProject directory
video-project/ Created in your repository by the workflow, and yours to read and edit.
Skill installed
bountex-motion6 licensed phases · 4 modes · v1.1.0
What it produces
Product and brand films
What is distinctive
Story-led. It inspects your site and repository before it asks anything, runs an adaptive interview, and turns the answers into a creative brief and a production prompt before a single frame is animated.
What is inside Film Kit
One file per phase, served on demand. What each phase is for is its own title, taken from the kit registry — everything below the titles is the licensed method, and this page does not describe it.
interviewAdaptive interview & context inspection
Loaded by brief, prompt, full, default
references/interview.mddirectionCreative direction & story selection
Loaded by brief, full, default
references/creative-director.mdpromptUniversal production prompt
Loaded by prompt, full, default
references/production-prompt.mdcritiqueIndependent critic loop & quality bar
Loaded by full, build, default
references/quality-bar.mdbuildDeterministic composition & render contract
Loaded by build, full, default
references/hyperframes.mdtemplateCanonical creative brief template
Loaded by brief, full, default
templates/creative-brief.mdModes
A mode decides how far the workflow goes. Pass it as the first word after the trigger, or to playbook --mode. The phases a mode loads are not a separate list: they are every phase whose usedBy names that mode.
| Mode | What it produces | Phases loaded |
|---|---|---|
brief | Interview and direction only. Produces the creative brief; nothing is animated. | interviewdirectiontemplate |
prompt | Reads the brief you already have and produces the production prompt; nothing is animated. | interviewprompt |
build | Uses the brief and the prompt you have: storyboard, composition, render. | critiquebuild |
full | The whole run: intake to delivered renders, with the critic loop. | interviewdirectionpromptcritiquebuildtemplate |
With no mode word the workflow runs its default flow: every phase in this kit lists default, so the whole playbook is in play. It inspects first, then continues according to what you asked for — writing its state into video-project/. See the file layout.
Kit 2 of 2 · v1.1.0
Reel Kit
A motion designer and production orchestrator for short, music-led motion-design reels: concept, audio bed, beat sheet, storyboard, a mandatory review gate, a hero shot, the build, and an independent critic loop.
Trigger
$/bountex-motion-reelProject directory
motion-project/ Created in your repository by the workflow, and yours to read and edit.
Skill installed
bountex-motion-reel7 licensed phases · 3 modes · v1.1.0
What it produces
Short, music-led motion-design reels
What is distinctive
Beat-led: one visual idea, cut to the music. It stops at a mandatory review gate — nothing is built until you approve the concept, the beat sheet, and the storyboard.
What is inside Reel Kit
One file per phase, served on demand. What each phase is for is its own title, taken from the kit registry — everything below the titles is the licensed method, and this page does not describe it.
conceptConcept: one visual idea, mode and devices
Loaded by default, graphic, ui, full
references/visual-language.mdaudioAudio bed: resolve the track and place it
Loaded by default, graphic, ui, full
references/audio-sync.mdbeatsBeat sheet: map the concept to the beat grid
Loaded by default, graphic, ui, full
references/audio-sync.mdstoryboardStoryboard: per-shot timing, movement and transitions
Loaded by default, graphic, ui, full
templates/concept.mdreviewMandatory review gate before any build
Loaded by default, graphic, ui, full
references/quality-bar.mdmotionDesign system, hero shot and the full build
Loaded by default, graphic, ui, full
references/motion-language.mdcritiqueIndependent critic loop & quality bar
Loaded by default, graphic, ui, full
references/quality-bar.mdModes
A mode decides how far the workflow goes. Pass it as the first word after the trigger, or to playbook --mode. The phases a mode loads are not a separate list: they are every phase whose usedBy names that mode.
| Mode | What it produces | Phases loaded |
|---|---|---|
graphic | Runs the reel in the graphic visual mode. The concept picks the devices. | conceptaudiobeatsstoryboardreviewmotioncritique |
ui | Runs the reel in the ui visual mode. The concept picks the devices. | conceptaudiobeatsstoryboardreviewmotioncritique |
full | Every phase end to end; the concept decides the visual mode. | conceptaudiobeatsstoryboardreviewmotioncritique |
With no mode word the workflow runs its default flow: every phase in this kit lists default, so the whole playbook is in play. It inspects first, then continues according to what you asked for — writing its state into motion-project/. See the file layout.
Where each part lives
Your disk holds the shape. The server holds the method.
This split is the commercial core of the product, and it is the same for both kits — which is why the two can share one license without sharing any content.
The public skeleton
Written by install <kit>, versioned, SHA-256 verified, and refreshed in place by update. It is the workflow’s order, its principles, and the state it keeps. It is deliberately insufficient on its own, and it is safe to read — there are no thresholds, prompt templates, or critic procedures in it. Each kit writes its own runner and its own trigger, so both can live in one project.
Film Kit
The runner skill
skills/bountex-motion/SKILL.mdThe shape of the workflow: the order of the phases, the principles that never change, and the instruction to load each phase from the server before doing that phase’s work.
The command registration
commands/bountex-motion.mdThe /bountex-motion trigger your tool discovers, and the argument parsing that turns a mode word, a path, or a URL into an invocation.
Reel Kit
The runner skill
skills/bountex-motion-reel/SKILL.mdThe shape of the workflow: the order of the phases, the principles that never change, and the instruction to load each phase from the server before doing that phase’s work.
The command registration
commands/bountex-motion-reel.mdThe /bountex-motion-reel trigger your tool discovers, and the argument parsing that turns a mode word, a path, or a URL into an invocation.
The licensed substance
Before your agent does the work of a phase, it fetches that phase from the license server. The CLI prints it to stdout, the agent reads it, and it exists in that session only — never in your repository, never in a commit, never in the artifact you downloaded. It is available only to an entitled, seat-bound device, and it stops arriving when the subscription stops.
Film Kit · 6 phases
$npx bountex-motion playbook <phase> --kit filmReel Kit · 7 phases
$npx bountex-motion playbook <phase> --kit reel
Read what that means for you in the documentation overview.
Supported tools
Both kits, 7 layouts.
The installer detects the tool from your project and writes only the paths it discovers. Each kit registers its own trigger, so either one — or both — can live in the same tool. Force one with --harness, or write every layout with --all.
| Tool | Trigger | Install root |
|---|---|---|
| Claude Code claude-code |
| .claude |
| Cursor cursor |
| .cursor |
| Codex CLI codex |
| .agents |
| OpenCode opencode |
| .opencode |
| GitHub Copilot copilot |
| .github |
| Antigravity CLI antigravity |
| .agentsFilm Kit: Run the plugin install step your CLI reports, then start /bountex-motion.Reel Kit: Run the plugin install step your CLI reports, then start /bountex-motion-reel. |
| Kimi Code kimi |
| .bountex-motionFilm Kit: Run `/plugins install .bountex-motion/film`, start a fresh session, then `/bountex-motion:film`.Reel Kit: Run `/plugins install .bountex-motion/reel`, start a fresh session, then `/bountex-motion:reel`. |
One license key covers every tool in this table. Install either kit into as many of them as you like — the 3-seat limit is on machines, not on tools.
The rules that do not move
What both kits refuse to do is most of what you are buying.
These hold in every mode, on every tool, whatever a phase says. They are also the reason the output does not look generated.
- Claim to have inspected material it did not read. If a source is missing, empty, or unreachable, it says so once and asks only the minimum.
- Invent a fact, a number, a customer, a testimonial, or a capability — or present generated media as evidence of something real.
- Open with a fixed questionnaire instead of inspecting what already exists.
- Animate everything, or leave dead frames. A deliberate pause is deliberate.
- Declare the work finished on the builder’s own judgment. A fresh critic runs after every correction pass.
- Write the licensed playbook to disk, into a commit, or into a document.
On your machine
It orchestrates the build. It does not render for you in the cloud.
We would rather say this plainly on the sales page than have you discover it after paying.
What the render needs
- Node.js 22 or newer for the HyperFrames toolchain
- FFmpeg on your PATH for encoding and audio
- A Chrome or Chromium install to draw the frames
npx bountex-motion doctor checks all three before a session wastes your time.
Why it works this way
A flat monthly price with unlimited work is only possible if the rendering happens on hardware you already pay for. It also means your footage, your briefs, and your renders never leave your machine — nothing about your project is uploaded.
The tools around it are not ours
HyperFrames, FFmpeg, Chrome, and the AI coding tools you run the workflow inside are third-party products with their own terms. They are not affiliated with BountEx Labs, LLC and we do not resell them.
One license key. Both kits. Every tool.
3 device seats on one key, a 14-day refund, and the whole library — Film Kit and Reel Kit — while you are subscribed.
Questions before you buy? The FAQ answers the awkward ones, and support is Telegram @bountexlabs.