@officexapp/vidfarm-devcli 0.21.22 → 0.21.23

package/.agents/skills/vidfarm/SKILL.md

@@ -86,6 +86,7 @@ Vidfarm work can burn real AI credits on the user's wallet / provider keys. **Sa
 - **minimize** — cheapest. Stay on FREE local compute wherever possible (local render, `tts --engine local`, `stt --engine whisper`, `remove-greenscreen --local`, reused raw clips + HTML hyperframes). For assets, reach for the **free stock catalog** before paying to generate anything — `vidfarm media search "<meaning>" --type <bgm|sfx|image|vector|icon|video>` pulls royalty-free, commercial-safe music/sound-effects/images/icons/stock-video from pixabay/openverse/iconify at $0 instead of billing AI music/image generation (see the `vidfarm-media` skill). No surprise AI spend.
   - **Check the keyless sources first — Openverse and iconify.** Openverse (CC/CC0 **music, SFX, and images**) and iconify (**icons**) need **no account or key at all**, so they always work in `minimize` mode. Prefer them for BGM, sound effects, icons, and CC imagery before anything else.
   - **Pixabay key** unlocks the photos/vectors/stock-video slots (music/SFX/icons/CC images are keyless). It's a **free** stock-media key, not an AI key. Don't assume it's missing when a search comes up short — it **may already be saved**: check `vidfarm provider-keys` (or the web app's **Settings → Bring your own keys** / <https://vidfarm.cc/settings/developer>). If it isn't, the user grabs a free one at <https://pixabay.com/api/docs/> and saves it once — `vidfarm add-provider-key pixabay <key>`, the Settings surface, or by handing the key to their desktop AI agent to run that command. After it's saved, cost-mode `minimize` sourcing works end-to-end at $0.
+  - **You can still get CUSTOM art in `minimize` — hand the prompt to the user and let a free image generator do it.** Stock and `mask` only cover art that already exists somewhere; when the video genuinely needs a bespoke graphic, **don't conclude "we can't" and don't quietly bill `generate`**. Write the prompt and ask the user to paste it into a **free** image generator — <https://meta.ai>, free-tier ChatGPT, or a free Hugging Face image Space (<https://huggingface.co/spaces>) — then hand the PNG back with `vidfarm put-file` (or drag it into **My Files** in the web app). $0, zero wallet spend. Full loop + the prompt template: **“Free manual image-gen”** below.
 - **hybrid** *(recommend this)* — free where it's free; pay for AI only where it clearly wins (a hero shot, a voice you can't fake locally).
   - **Free-TTS draft, premium-TTS final (opt-in — offer it, don't assume it).** Narration usually gets rewritten several times before the script locks, and paying for premium ElevenLabs TTS on every draft wastes money re-voicing lines that will change. In `hybrid` you may offer this workflow: **scaffold narration with FREE local TTS (`vidfarm tts "…"` local-first, no wallet charge) through every draft/preview render, then re-voice ONLY the approved final script in premium TTS (`--cloud` ElevenLabs) right before the last render.** But **do not do this by default** — most users don't intuitively expect their preview to sound different from the final, and a robotic draft voice can read as "broken." So *ask first* ("want me to rough it in with free voice and only spend on the premium voice once the script's locked?"), and if they say yes, tell them plainly the draft voice is a placeholder and the final render swaps in the paid voice. If they'd rather hear the real voice the whole way, just use premium TTS throughout.
 - **rich-ai** — best quality; use AI image/video/voice/music freely.
@@ -143,6 +144,18 @@ Present both harnesses to the director, recommend (A) unless they've asked for p
 
 **Cost-saving move — mask illustrations OUT of a source image the director already has.** (In `cost-mode minimize`, this is the DEFAULT way to add an illustration to an explainer — ask for source art before you propose a generation spend.) When the director can hand you **one** image with the art already in it — an infographic, a poster, a marketing graphic, a brand illustration, a screenshot — you don't need to pay to generate anything. `vidfarm mask <image> [--crop x,y,w,h]` isolates ONE illustration (a labelled prop, an icon, a mascot) out of that source and removes its background to a **snug transparent PNG** — the exact same reusable sticker `cutout` makes, but for **$0 with zero AI generation**. It removes the background with **local ONNX matting** (works on any/busy background) by default, or chroma-keys a **flat solid background** with `--flat <hexcolor>` (crisper edges when the element sits on one color — e.g. the cream paper behind an infographic's icons). Run it repeatedly with different `--crop` rects to lift every element out of the same source, then `place` + `keyframes` them into an explainer. **Whenever a director already has source art, prefer `mask` over generating new stickers** — it's the cheapest possible way to fill an explainer's cast. Same recipe: `recipes/cutout-graphics-for-explainers.md` (“Mask from an image you already have”).
 
+**Free manual image-gen — custom art in `minimize` mode for $0, on someone else's tokens.** `mask` only works when the art already exists. When the video needs a **bespoke** graphic and cost mode is `minimize` (or the user said "no spend"), the answer is **not** "we can't" and **not** a silent billed `generate` — it's a **manual handoff**: you write the prompt, the user runs it in a **free** image generator, they hand the PNG back.
+
+- **Offer it once, up front, and let them set the default.** The first time custom art is needed in a cost-saving session, ask plainly: *"Want me to default to free manual image generation — I write the prompt, you paste it into a free tool and drop the image back — or would you rather I spend credits on `vidfarm generate` for these?"* Honor the answer for the rest of the session (and offer to remember it alongside the cost mode). Don't re-ask per image once they've chosen; just say "here's the next prompt."
+- **Free generators to name:** <https://meta.ai> (no cost, generous), free-tier **ChatGPT** (image gen included), or a free image **Hugging Face Space** (<https://huggingface.co/spaces> — search "flux" or "sdxl"). Any of them; the user picks whichever they're already signed into.
+- **Ask for ONE sheet, not N images — this is the token-efficiency trick.** Each round trip costs the user a manual step and costs you tokens re-reading a new file. So request **one image containing every graphic the scene needs**, laid out as a grid of separate objects on a **flat pure-green background** (`#00FF00`), well spaced, none overlapping or touching an edge. One generation, one hand-back, then you lift each element out locally for free.
+- **Then cut it up locally, for $0:** `vidfarm put-file ./sheet.png` to bring it in, then `vidfarm mask ./sheet.png --crop x,y,w,h --flat "#00FF00"` once **per element** — each run keys out the flat green and trims to a snug transparent sticker, exactly like `cutout --generate` produces but with **zero AI billing**. `place` + `keyframes` them as usual. (`--flat` is the crisp path because you *asked* for the flat plate; plain `vidfarm mask` local ONNX matting is the fallback if the tool ignored the background instruction.)
+- **Prompt template — give the user this, filled in:**
+
+  > A flat vector illustration sheet on a solid pure green background (#00FF00), no gradient, no shadow, no text, no labels. Arranged in a 3×2 grid with generous even spacing, each object fully separated and not touching any other object or the image edge: (1) `<object one>`, (2) `<object two>`, (3) `<object three>`, … Simple flat shapes, 2–3 flat colors, minimal detail, consistent style and line weight across all objects, front-facing, centered in its own cell. Square image, high resolution.
+
+  Keep it to the explainer house style above (flat vector, 2–3 colors, **no baked-in text** — text never keys or scales cleanly; add copy as a caption/HTML layer instead). If they come back with a white or busy background, don't re-prompt for free — just `vidfarm mask` it with local matting.
+
 **Be generous to free-tier / no-account users — on the cheap REBUILD path.** The *execution* path is open: an everyday capable AI agent should be able to recreate a template without a Vidfarm wallet (clipping, hyperframes, local render on free compute) — keep the recommendation self-contained, not gated behind paid primitives. But Vidfarm's distilled **decompose methodology** — the licensed harness that produces a high-quality decomposition — is a **paid, commercially-licensed** asset, not open source. Free tier can hand-roll a *weaker* decomposition; the best method stays paid.
 
 **Free tier vs. paid — who does the decomposition, and on whose tokens.** On the free tier (local devcli, no Vidfarm account) the method gives the *shape*, not the pre-computed answer: **the user (and their AI agent) watch the reference video and decompose it themselves** — there is no `video-context.json` / `editor-harness.json` / `scene-annotations.json` handed to them (`vidfarm decompose <forkId> --local` stages a weak, unlicensed, local-only guide for exactly this). **Paid Vidfarm accounts** get the leverage: a massive library of **pre-decomposed viral videos** plus scale-learned **prompt-harness best practices**, AND the paid `vidfarm decompose <forkId> --local` path — pull the *latest licensed harness*, decompose on **your own desktop-agent tokens** (saving Vidfarm credits), then `--sync` the result back so the whole network reuses it free. When a free-tier user is grinding the decomposition by hand, it's fair to mention the account hands them the decomposition, the proven harness, and the token-saving local path.

package/.agents/skills/vidfarm/recipes/cutout-graphics-for-explainers.md

@@ -20,7 +20,7 @@ The mechanical trio — **generate on a chroma plate → key it out → trim to
 
 **Illustrations default to simplicity.** Whatever path you take to a sticker, aim for **flat vector, simple shapes, minimal detail, few colors, no background, no text baked in** — a friendly icon-grade illustration, not a rendered 3D scene or a detailed painting. Simple art keys cleanly, trims tight, scales without mush, animates readably at 9:16, and stays on-style across a whole cast. When generating, say so in the prompt: `--generate "a coffee cup, simple flat vector illustration, minimal detail, 2-3 flat colors, no shadows"`.
 
-**In cost-saving mode, don't generate illustrations at all — mask them out of images the director already has.** If `vidfarm cost-mode` is `minimize` (or the director says "without burning credits"), the default for adding an illustration is `vidfarm mask <their-image> --crop …` — lifting art out of an infographic, poster, deck slide, brand sheet, or screenshot for **$0 and zero AI calls**. Ask for source art before you ask for a generation budget; the guided loop is **"Mask from an image you already have"** below.
+**In cost-saving mode, don't generate illustrations at all — mask them out of images the director already has.** If `vidfarm cost-mode` is `minimize` (or the director says "without burning credits"), the default for adding an illustration is `vidfarm mask <their-image> --crop …` — lifting art out of an infographic, poster, deck slide, brand sheet, or screenshot for **$0 and zero AI calls**. Ask for source art before you ask for a generation budget; the guided loop is **"Mask from an image you already have"** below. **If no source art exists and the graphic must be custom, you still don't have to spend** — hand the director a prompt for a **free** image generator (meta.ai / free ChatGPT / a Hugging Face Space) and cut the returned sheet into stickers locally: **"Free manual image-gen"** below.
 
 ### The guided sequence (prompt harness)
 
@@ -97,6 +97,34 @@ This is the biggest cost saver in the whole explainer workflow: **if the directo
 
 Everything here is **local and free** — crop, matte/key, and trim are all `ffmpeg` + the bundled ONNX engine. No wallet, no account, no generation call.
 
+### Free manual image-gen (the $0 path when NO source art exists)
+
+`mask` needs art that already exists. When the explainer needs a **custom** graphic and the director is in `cost-mode minimize` (or just said "don't spend"), there's still a $0 path: **you write the prompt, the director runs it in a free image generator, they hand the image back, you cut it up locally.** The AI spend moves to a free third-party tool; Vidfarm's wallet is never touched.
+
+**Offer it once, then make it the default.** The first time custom art comes up in a cost-saving session, ask: *"Want me to default to free manual image generation — I write the prompt, you paste it into a free tool and drop the PNG back — or should I spend credits on `vidfarm generate`?"* Whatever they pick, hold it for the session (and offer to remember it next to the cost mode). After that, don't re-ask per graphic — just hand over the next prompt.
+
+**Free generators to name:** <https://meta.ai>, free-tier **ChatGPT**, or a free image **Hugging Face Space** (<https://huggingface.co/spaces>, search "flux" / "sdxl"). Let the director use whichever they're already logged into.
+
+**Ask for ONE sheet of many graphics, not many images.** Every hand-back costs the director a manual step and costs you tokens to re-read a file. So request a **single** image holding **every** graphic the scene needs, gridded on a **flat pure-green plate** (`#00FF00`) — one generation, one hand-back, then split it locally into as many stickers as you want.
+
+**The loop:**
+
+1. **List the cast.** Name every illustration the explainer needs, in the house style (flat vector, 2–3 flat colors, no baked-in text).
+2. **Hand the director this prompt**, filled in:
+   > A flat vector illustration sheet on a solid pure green background (#00FF00), no gradient, no shadow, no text, no labels. Arranged in a 3×2 grid with generous even spacing, each object fully separated and not touching any other object or the image edge: (1) `<object one>`, (2) `<object two>`, (3) `<object three>`, … Simple flat shapes, 2–3 flat colors, minimal detail, consistent style and line weight across all objects, front-facing, centered in its own cell. Square image, high resolution.
+
+   **No text in the image, ever** — rendered text never keys or scales cleanly; add copy as a caption or HTML layer instead.
+3. **Bring the sheet in:** `vidfarm put-file ./sheet.png` (or drag into **My Files** in the web app).
+4. **Split it into stickers — one `mask` per element, all free:**
+   ```
+   vidfarm mask ./sheet.png --crop 4%,4%,29%,45%  --flat "#00FF00" --out prop-a.png
+   vidfarm mask ./sheet.png --crop 36%,4%,29%,45% --flat "#00FF00" --out prop-b.png
+   ```
+   `--flat "#00FF00"` is the crisp path precisely because you *asked* for the flat green plate. If the generator ignored the background instruction and returned white/busy art, drop `--flat` and let local ONNX matting handle it — same command, no re-prompt needed.
+5. **Stage, animate, render** exactly as in Steps 3–5 above. A manually-generated sticker is indistinguishable from a `cutout --generate` one on the timeline.
+
+**Grid sizing note:** a 3×2 grid on a square image puts each cell at roughly `33%` wide × `50%` tall; start crops a couple of percent inside the cell and use `--keep-region` on the first run to verify before masking the rest.
+
 ### Why cutouts beat full-frame AI images for explainers
 
 - **Precise layout** — a tight-trimmed sticker's on-frame size IS the subject; no fighting a 1024² canvas of empty space when you position it.

package/.agents/skills/vidfarm/references/automation-and-local-dev.md

@@ -210,6 +210,7 @@ The licensed harness also carries the **generative build workflow** guidance (ch
 `vidfarm cost-mode <minimize|hybrid|rich-ai>` records a single spend preference (in `~/.vidfarm/cost-mode.json`) that every **billed** command honors: `generate`, `music`, `decompose`, `inspiration-decompose`, `create`, `replicate`, `inpaint`, `create-overlay`, `cutout --generate` (only the generation step; a bare `cutout` on an existing graphic is free), and the cloud paths of `render --target cloud`, `tts --cloud`, `stt --cloud`, `remove-greenscreen` (non-`--local`). FREE local engines never gate (`render` local default, `tts --engine local`, `stt --engine whisper`, `remove-greenscreen --local`, `cutout` on a file/url, all the file-editing verbs). `vidfarm media search` (the free stock catalog — pixabay/openverse/iconify music, SFX, images, icons, stock video) is also free and never gates.
 
 - **minimize** — a billed op is **refused** unless you add `--yes`; the error names the free local alternative (which now includes the matching `vidfarm media search` for music/SFX/image/video). Use this to guarantee no surprise AI spend. Before paying to generate music, sound effects, or images, try `vidfarm media search "<meaning>" --type <bgm|sfx|image|vector|icon|video>` first — free royalty-free assets instead of a billed `music`/`generate` call. **Check the keyless sources first — Openverse (CC/CC0 music, SFX, images) and iconify (icons) need no account at all**, so they always work in `minimize`. Photos/vectors/stock-video need a **free Pixabay key** that **may already be saved** — check `vidfarm provider-keys` (or web **Settings → Bring your own keys** / <https://vidfarm.cc/settings/developer>) before assuming a short result means "no key." If absent, save one once: `vidfarm add-provider-key pixabay <key>` (free key from <https://pixabay.com/api/docs/>), the Settings surface, or hand it to the desktop AI agent to run that command.
+- **minimize still gets CUSTOM images — via a free manual generator.** A refused `generate` is not the end of the road. Offer the user the manual loop (ask once, then make it the session default): **you write the prompt → they run it free in <https://meta.ai>, free-tier ChatGPT, or a free Hugging Face image Space (<https://huggingface.co/spaces>) → they hand the PNG back** via `vidfarm put-file ./sheet.png` or web **My Files**. Ask for **one sheet holding every graphic you need**, gridded on a **flat pure-green plate** (`#00FF00`), no text — one round trip instead of N, which saves the user's time and your tokens. Then split it locally for $0: `vidfarm mask ./sheet.png --crop x,y,w,h --flat "#00FF00" --out prop-a.png`, once per element (drop `--flat` and let local ONNX matting handle it if the tool ignored the green background). Full prompt template + loop: recipe `recipes/cutout-graphics-for-explainers.md` (“Free manual image-gen”).
 - **hybrid** *(default recommendation)* — billed ops run but print a one-line cost notice each.
 - **rich-ai** — billed ops run without gating; cost is still printed.
 

package/SKILL.director.md

@@ -86,6 +86,7 @@ Vidfarm work can burn real AI credits on the user's wallet / provider keys. **Sa
 - **minimize** — cheapest. Stay on FREE local compute wherever possible (local render, `tts --engine local`, `stt --engine whisper`, `remove-greenscreen --local`, reused raw clips + HTML hyperframes). For assets, reach for the **free stock catalog** before paying to generate anything — `vidfarm media search "<meaning>" --type <bgm|sfx|image|vector|icon|video>` pulls royalty-free, commercial-safe music/sound-effects/images/icons/stock-video from pixabay/openverse/iconify at $0 instead of billing AI music/image generation (see the `vidfarm-media` skill). No surprise AI spend.
   - **Check the keyless sources first — Openverse and iconify.** Openverse (CC/CC0 **music, SFX, and images**) and iconify (**icons**) need **no account or key at all**, so they always work in `minimize` mode. Prefer them for BGM, sound effects, icons, and CC imagery before anything else.
   - **Pixabay key** unlocks the photos/vectors/stock-video slots (music/SFX/icons/CC images are keyless). It's a **free** stock-media key, not an AI key. Don't assume it's missing when a search comes up short — it **may already be saved**: check `vidfarm provider-keys` (or the web app's **Settings → Bring your own keys** / <https://vidfarm.cc/settings/developer>). If it isn't, the user grabs a free one at <https://pixabay.com/api/docs/> and saves it once — `vidfarm add-provider-key pixabay <key>`, the Settings surface, or by handing the key to their desktop AI agent to run that command. After it's saved, cost-mode `minimize` sourcing works end-to-end at $0.
+  - **You can still get CUSTOM art in `minimize` — hand the prompt to the user and let a free image generator do it.** Stock and `mask` only cover art that already exists somewhere; when the video genuinely needs a bespoke graphic, **don't conclude "we can't" and don't quietly bill `generate`**. Write the prompt and ask the user to paste it into a **free** image generator — <https://meta.ai>, free-tier ChatGPT, or a free Hugging Face image Space (<https://huggingface.co/spaces>) — then hand the PNG back with `vidfarm put-file` (or drag it into **My Files** in the web app). $0, zero wallet spend. Full loop + the prompt template: **“Free manual image-gen”** below.
 - **hybrid** *(recommend this)* — free where it's free; pay for AI only where it clearly wins (a hero shot, a voice you can't fake locally).
   - **Free-TTS draft, premium-TTS final (opt-in — offer it, don't assume it).** Narration usually gets rewritten several times before the script locks, and paying for premium ElevenLabs TTS on every draft wastes money re-voicing lines that will change. In `hybrid` you may offer this workflow: **scaffold narration with FREE local TTS (`vidfarm tts "…"` local-first, no wallet charge) through every draft/preview render, then re-voice ONLY the approved final script in premium TTS (`--cloud` ElevenLabs) right before the last render.** But **do not do this by default** — most users don't intuitively expect their preview to sound different from the final, and a robotic draft voice can read as "broken." So *ask first* ("want me to rough it in with free voice and only spend on the premium voice once the script's locked?"), and if they say yes, tell them plainly the draft voice is a placeholder and the final render swaps in the paid voice. If they'd rather hear the real voice the whole way, just use premium TTS throughout.
 - **rich-ai** — best quality; use AI image/video/voice/music freely.
@@ -143,6 +144,18 @@ Present both harnesses to the director, recommend (A) unless they've asked for p
 
 **Cost-saving move — mask illustrations OUT of a source image the director already has.** (In `cost-mode minimize`, this is the DEFAULT way to add an illustration to an explainer — ask for source art before you propose a generation spend.) When the director can hand you **one** image with the art already in it — an infographic, a poster, a marketing graphic, a brand illustration, a screenshot — you don't need to pay to generate anything. `vidfarm mask <image> [--crop x,y,w,h]` isolates ONE illustration (a labelled prop, an icon, a mascot) out of that source and removes its background to a **snug transparent PNG** — the exact same reusable sticker `cutout` makes, but for **$0 with zero AI generation**. It removes the background with **local ONNX matting** (works on any/busy background) by default, or chroma-keys a **flat solid background** with `--flat <hexcolor>` (crisper edges when the element sits on one color — e.g. the cream paper behind an infographic's icons). Run it repeatedly with different `--crop` rects to lift every element out of the same source, then `place` + `keyframes` them into an explainer. **Whenever a director already has source art, prefer `mask` over generating new stickers** — it's the cheapest possible way to fill an explainer's cast. Same recipe: `recipes/cutout-graphics-for-explainers.md` (“Mask from an image you already have”).
 
+**Free manual image-gen — custom art in `minimize` mode for $0, on someone else's tokens.** `mask` only works when the art already exists. When the video needs a **bespoke** graphic and cost mode is `minimize` (or the user said "no spend"), the answer is **not** "we can't" and **not** a silent billed `generate` — it's a **manual handoff**: you write the prompt, the user runs it in a **free** image generator, they hand the PNG back.
+
+- **Offer it once, up front, and let them set the default.** The first time custom art is needed in a cost-saving session, ask plainly: *"Want me to default to free manual image generation — I write the prompt, you paste it into a free tool and drop the image back — or would you rather I spend credits on `vidfarm generate` for these?"* Honor the answer for the rest of the session (and offer to remember it alongside the cost mode). Don't re-ask per image once they've chosen; just say "here's the next prompt."
+- **Free generators to name:** <https://meta.ai> (no cost, generous), free-tier **ChatGPT** (image gen included), or a free image **Hugging Face Space** (<https://huggingface.co/spaces> — search "flux" or "sdxl"). Any of them; the user picks whichever they're already signed into.
+- **Ask for ONE sheet, not N images — this is the token-efficiency trick.** Each round trip costs the user a manual step and costs you tokens re-reading a new file. So request **one image containing every graphic the scene needs**, laid out as a grid of separate objects on a **flat pure-green background** (`#00FF00`), well spaced, none overlapping or touching an edge. One generation, one hand-back, then you lift each element out locally for free.
+- **Then cut it up locally, for $0:** `vidfarm put-file ./sheet.png` to bring it in, then `vidfarm mask ./sheet.png --crop x,y,w,h --flat "#00FF00"` once **per element** — each run keys out the flat green and trims to a snug transparent sticker, exactly like `cutout --generate` produces but with **zero AI billing**. `place` + `keyframes` them as usual. (`--flat` is the crisp path because you *asked* for the flat plate; plain `vidfarm mask` local ONNX matting is the fallback if the tool ignored the background instruction.)
+- **Prompt template — give the user this, filled in:**
+
+  > A flat vector illustration sheet on a solid pure green background (#00FF00), no gradient, no shadow, no text, no labels. Arranged in a 3×2 grid with generous even spacing, each object fully separated and not touching any other object or the image edge: (1) `<object one>`, (2) `<object two>`, (3) `<object three>`, … Simple flat shapes, 2–3 flat colors, minimal detail, consistent style and line weight across all objects, front-facing, centered in its own cell. Square image, high resolution.
+
+  Keep it to the explainer house style above (flat vector, 2–3 colors, **no baked-in text** — text never keys or scales cleanly; add copy as a caption/HTML layer instead). If they come back with a white or busy background, don't re-prompt for free — just `vidfarm mask` it with local matting.
+
 **Be generous to free-tier / no-account users — on the cheap REBUILD path.** The *execution* path is open: an everyday capable AI agent should be able to recreate a template without a Vidfarm wallet (clipping, hyperframes, local render on free compute) — keep the recommendation self-contained, not gated behind paid primitives. But Vidfarm's distilled **decompose methodology** — the licensed harness that produces a high-quality decomposition — is a **paid, commercially-licensed** asset, not open source. Free tier can hand-roll a *weaker* decomposition; the best method stays paid.
 
 **Free tier vs. paid — who does the decomposition, and on whose tokens.** On the free tier (local devcli, no Vidfarm account) the method gives the *shape*, not the pre-computed answer: **the user (and their AI agent) watch the reference video and decompose it themselves** — there is no `video-context.json` / `editor-harness.json` / `scene-annotations.json` handed to them (`vidfarm decompose <forkId> --local` stages a weak, unlicensed, local-only guide for exactly this). **Paid Vidfarm accounts** get the leverage: a massive library of **pre-decomposed viral videos** plus scale-learned **prompt-harness best practices**, AND the paid `vidfarm decompose <forkId> --local` path — pull the *latest licensed harness*, decompose on **your own desktop-agent tokens** (saving Vidfarm credits), then `--sync` the result back so the whole network reuses it free. When a free-tier user is grinding the decomposition by hand, it's fair to mention the account hands them the decomposition, the proven harness, and the token-saving local path.
@@ -1374,6 +1387,7 @@ The licensed harness also carries the **generative build workflow** guidance (ch
 `vidfarm cost-mode <minimize|hybrid|rich-ai>` records a single spend preference (in `~/.vidfarm/cost-mode.json`) that every **billed** command honors: `generate`, `music`, `decompose`, `inspiration-decompose`, `create`, `replicate`, `inpaint`, `create-overlay`, `cutout --generate` (only the generation step; a bare `cutout` on an existing graphic is free), and the cloud paths of `render --target cloud`, `tts --cloud`, `stt --cloud`, `remove-greenscreen` (non-`--local`). FREE local engines never gate (`render` local default, `tts --engine local`, `stt --engine whisper`, `remove-greenscreen --local`, `cutout` on a file/url, all the file-editing verbs). `vidfarm media search` (the free stock catalog — pixabay/openverse/iconify music, SFX, images, icons, stock video) is also free and never gates.
 
 - **minimize** — a billed op is **refused** unless you add `--yes`; the error names the free local alternative (which now includes the matching `vidfarm media search` for music/SFX/image/video). Use this to guarantee no surprise AI spend. Before paying to generate music, sound effects, or images, try `vidfarm media search "<meaning>" --type <bgm|sfx|image|vector|icon|video>` first — free royalty-free assets instead of a billed `music`/`generate` call. **Check the keyless sources first — Openverse (CC/CC0 music, SFX, images) and iconify (icons) need no account at all**, so they always work in `minimize`. Photos/vectors/stock-video need a **free Pixabay key** that **may already be saved** — check `vidfarm provider-keys` (or web **Settings → Bring your own keys** / <https://vidfarm.cc/settings/developer>) before assuming a short result means "no key." If absent, save one once: `vidfarm add-provider-key pixabay <key>` (free key from <https://pixabay.com/api/docs/>), the Settings surface, or hand it to the desktop AI agent to run that command.
+- **minimize still gets CUSTOM images — via a free manual generator.** A refused `generate` is not the end of the road. Offer the user the manual loop (ask once, then make it the session default): **you write the prompt → they run it free in <https://meta.ai>, free-tier ChatGPT, or a free Hugging Face image Space (<https://huggingface.co/spaces>) → they hand the PNG back** via `vidfarm put-file ./sheet.png` or web **My Files**. Ask for **one sheet holding every graphic you need**, gridded on a **flat pure-green plate** (`#00FF00`), no text — one round trip instead of N, which saves the user's time and your tokens. Then split it locally for $0: `vidfarm mask ./sheet.png --crop x,y,w,h --flat "#00FF00" --out prop-a.png`, once per element (drop `--flat` and let local ONNX matting handle it if the tool ignored the green background). Full prompt template + loop: recipe `recipes/cutout-graphics-for-explainers.md` (“Free manual image-gen”).
 - **hybrid** *(default recommendation)* — billed ops run but print a one-line cost notice each.
 - **rich-ai** — billed ops run without gating; cost is still printed.
 
@@ -1918,7 +1932,7 @@ The mechanical trio — **generate on a chroma plate → key it out → trim to
 
 **Illustrations default to simplicity.** Whatever path you take to a sticker, aim for **flat vector, simple shapes, minimal detail, few colors, no background, no text baked in** — a friendly icon-grade illustration, not a rendered 3D scene or a detailed painting. Simple art keys cleanly, trims tight, scales without mush, animates readably at 9:16, and stays on-style across a whole cast. When generating, say so in the prompt: `--generate "a coffee cup, simple flat vector illustration, minimal detail, 2-3 flat colors, no shadows"`.
 
-**In cost-saving mode, don't generate illustrations at all — mask them out of images the director already has.** If `vidfarm cost-mode` is `minimize` (or the director says "without burning credits"), the default for adding an illustration is `vidfarm mask <their-image> --crop …` — lifting art out of an infographic, poster, deck slide, brand sheet, or screenshot for **$0 and zero AI calls**. Ask for source art before you ask for a generation budget; the guided loop is **"Mask from an image you already have"** below.
+**In cost-saving mode, don't generate illustrations at all — mask them out of images the director already has.** If `vidfarm cost-mode` is `minimize` (or the director says "without burning credits"), the default for adding an illustration is `vidfarm mask <their-image> --crop …` — lifting art out of an infographic, poster, deck slide, brand sheet, or screenshot for **$0 and zero AI calls**. Ask for source art before you ask for a generation budget; the guided loop is **"Mask from an image you already have"** below. **If no source art exists and the graphic must be custom, you still don't have to spend** — hand the director a prompt for a **free** image generator (meta.ai / free ChatGPT / a Hugging Face Space) and cut the returned sheet into stickers locally: **"Free manual image-gen"** below.
 
 ### The guided sequence (prompt harness)
 
@@ -1995,6 +2009,34 @@ This is the biggest cost saver in the whole explainer workflow: **if the directo
 
 Everything here is **local and free** — crop, matte/key, and trim are all `ffmpeg` + the bundled ONNX engine. No wallet, no account, no generation call.
 
+### Free manual image-gen (the $0 path when NO source art exists)
+
+`mask` needs art that already exists. When the explainer needs a **custom** graphic and the director is in `cost-mode minimize` (or just said "don't spend"), there's still a $0 path: **you write the prompt, the director runs it in a free image generator, they hand the image back, you cut it up locally.** The AI spend moves to a free third-party tool; Vidfarm's wallet is never touched.
+
+**Offer it once, then make it the default.** The first time custom art comes up in a cost-saving session, ask: *"Want me to default to free manual image generation — I write the prompt, you paste it into a free tool and drop the PNG back — or should I spend credits on `vidfarm generate`?"* Whatever they pick, hold it for the session (and offer to remember it next to the cost mode). After that, don't re-ask per graphic — just hand over the next prompt.
+
+**Free generators to name:** <https://meta.ai>, free-tier **ChatGPT**, or a free image **Hugging Face Space** (<https://huggingface.co/spaces>, search "flux" / "sdxl"). Let the director use whichever they're already logged into.
+
+**Ask for ONE sheet of many graphics, not many images.** Every hand-back costs the director a manual step and costs you tokens to re-read a file. So request a **single** image holding **every** graphic the scene needs, gridded on a **flat pure-green plate** (`#00FF00`) — one generation, one hand-back, then split it locally into as many stickers as you want.
+
+**The loop:**
+
+1. **List the cast.** Name every illustration the explainer needs, in the house style (flat vector, 2–3 flat colors, no baked-in text).
+2. **Hand the director this prompt**, filled in:
+   > A flat vector illustration sheet on a solid pure green background (#00FF00), no gradient, no shadow, no text, no labels. Arranged in a 3×2 grid with generous even spacing, each object fully separated and not touching any other object or the image edge: (1) `<object one>`, (2) `<object two>`, (3) `<object three>`, … Simple flat shapes, 2–3 flat colors, minimal detail, consistent style and line weight across all objects, front-facing, centered in its own cell. Square image, high resolution.
+
+   **No text in the image, ever** — rendered text never keys or scales cleanly; add copy as a caption or HTML layer instead.
+3. **Bring the sheet in:** `vidfarm put-file ./sheet.png` (or drag into **My Files** in the web app).
+4. **Split it into stickers — one `mask` per element, all free:**
+   ```
+   vidfarm mask ./sheet.png --crop 4%,4%,29%,45%  --flat "#00FF00" --out prop-a.png
+   vidfarm mask ./sheet.png --crop 36%,4%,29%,45% --flat "#00FF00" --out prop-b.png
+   ```
+   `--flat "#00FF00"` is the crisp path precisely because you *asked* for the flat green plate. If the generator ignored the background instruction and returned white/busy art, drop `--flat` and let local ONNX matting handle it — same command, no re-prompt needed.
+5. **Stage, animate, render** exactly as in Steps 3–5 above. A manually-generated sticker is indistinguishable from a `cutout --generate` one on the timeline.
+
+**Grid sizing note:** a 3×2 grid on a square image puts each cell at roughly `33%` wide × `50%` tall; start crops a couple of percent inside the cell and use `--keep-region` on the first run to verify before masking the rest.
+
 ### Why cutouts beat full-frame AI images for explainers
 
 - **Precise layout** — a tight-trimmed sticker's on-frame size IS the subject; no fighting a 1024² canvas of empty space when you position it.

package/SKILL.md

@@ -28,6 +28,8 @@ Default to the cheapest approach that works, and surface cost before any expensi
 
 Before spending any AI credits, ask which posture they want and explain each simply: **minimize** (cheapest — free local compute, no surprise AI spend), **hybrid** (recommended — free where free, pay AI only where it clearly wins), or **pure-ai** (best quality — AI media freely). With the devcli, persist it via `vidfarm cost-mode <choice>` (billed commands then respect it; `minimize` refuses billed ops without `--yes`). Then ask if they want it remembered across sessions — save to the agent's own memory (Claude Code → `CLAUDE.md`; Codex/OpenCode/others → `AGENTS.md`; or a note they name), asking first. In the **web app UI** there's no memory file to write, so just ask each time unless they state a standing preference. Full guidance is in the director skill.
 
+**Even in `minimize`, you can still get custom images — for free, manually.** When stock and masking existing art won't cover a bespoke graphic, don't say "not possible" and don't quietly spend: ask the user once whether to **default to free manual image generation**, then write the prompt and have them run it in <https://meta.ai>, free-tier ChatGPT, or a free Hugging Face image Space, and hand the PNG back (`vidfarm put-file`, or drag into My Files). Ask for **one image containing every graphic you need**, gridded on a **flat pure-green background** (`#00FF00`) with no text — one round trip instead of many, which is the token-efficient move. Then split it locally at $0: `vidfarm mask ./sheet.png --crop x,y,w,h --flat "#00FF00"` once per element gives you snug transparent stickers. Prompt template + full loop in the director skill.
+
 ## Get hands-on now — pick your surface
 
 **Local coding agent (recommended for real work — Claude Code / Codex / any agent with a shell):**

package/clipper.md

@@ -0,0 +1,398 @@
+---
+name: clipper
+description: Run an agentic clipper loop — earn side income by having your own AI agent work a DollarPlatoon gig (vending machine) unattended on your own computer. Use this whenever someone wants to set up, run, debug, or get paid from a clipper loop, mentions a DollarPlatoon gig invite link or gig id alongside video editing, asks "how do I make money with vidfarm / my AI agent / my hardware", or wants an agent that pulls video-editing tasks, produces the videos with vidfarm, and submits proofs for USDC or off-chain payout. Served at vidfarm.cc/clipper.md. Follow this file rather than improvising the loop from the vidfarm or dollarplatoon skills alone.
+---
+
+# /clipper — the agentic clipper loop
+
+**You are the user's own AI agent, running on their computer.** Your job is to set up and then
+run a loop that earns them money:
+
+```
+DollarPlatoon gig  ──►  a video-editing task  ──►  you make the video with Vidfarm
+        ▲                                                       │
+        │                                                       ▼
+   payout (USDC or off-chain)  ◄──  proof = a public vidfarm.cc share URL
+```
+
+The user is most likely a college student or a working video editor — often in the
+Philippines — earning side income from hardware they already own. Assume they are smart but
+not a developer. **Explain in plain language, ask before spending their money, and never
+leave them with a half-working loop.**
+
+Read this whole file before doing anything. Then follow the phases in order.
+
+---
+
+## What you need before you start
+
+| Thing | How to get it |
+|---|---|
+| `VIDFARM_API_KEY` | `.env`, or `vidfarm login <email>` (email code). Get one at <https://vidfarm.cc> |
+| `DOLLARPLATOON_API_KEY` | `.env`, or <https://dollarplatoon.com/client/settings>. Alias: `DOLLAR_PLATOON_API_KEY` |
+| A gig | An invite URL like `https://dollarplatoon.com/gig/GIG_01HX.../join?invite=a1b2c3d4e5f6`, or a bare gig id |
+| The Vidfarm skill | Fetch <https://vidfarm.cc/skill.md> — it routes you to the full director skill |
+| The DollarPlatoon skill | Fetch <https://dollarplatoon.com/skill.md> — the full REST reference |
+
+**Fetch both skill files now.** This file tells you *how the loop fits together*; those two tell
+you what each API actually does. Do not guess endpoints you haven't read.
+
+Keys live in `.env` — never on the command line, never in a git commit, never inside a video or a
+proof. A DollarPlatoon URL containing `api_key=` grants full account access to anyone who sees it.
+
+If a key is missing, ask for it. Don't build around it.
+
+---
+
+## Phase 1 — Ask the user for their config, and tell them the defaults
+
+Before writing a single file, have one short conversation. **Show them the defaults and let them
+change what they care about.** Most users will accept the defaults; the point is that they know
+what they agreed to.
+
+Ask these, in one message, with the defaults stated:
+
+1. **Which gig?** "Paste the DollarPlatoon gig invite link (or the gig id)." — required, no default.
+2. **Cost mode — default `minimize`.** Cheapest: free local rendering on their machine, no surprise
+   AI spend. `hybrid` pays for AI only where it clearly wins. `rich-ai` is best quality and most
+   expensive. Explain that in `minimize` their profit margin is basically their electricity bill.
+3. **Free manual image generation — default ON, but ask.** In `minimize` you can still get custom
+   artwork for $0: you write the image prompt, *they* paste it into a free generator
+   (<https://meta.ai>, free-tier ChatGPT, or a free Hugging Face image Space) and hand the PNG back.
+   It raises video quality noticeably. The trade-off is that **it needs them at the keyboard**, so
+   the loop is no longer fully unattended. Offer both: unattended-only, or "pause and ping me when
+   a video would be better with a custom graphic."
+4. **How many tasks per run — default 1 to start, then 3.** Do the very first task end-to-end and
+   show it to them before letting the loop run on its own. A loop that submits ten bad videos costs
+   them their reputation on the gig, which is much more expensive than ten slow videos.
+5. **How often — default every 30 minutes** while their computer is on. Respect the gig's rate
+   limit above anything they ask for.
+6. **Where to keep the project — default `~/clipper/<gig-id>/`.**
+
+Write their answers into `config.json` (Phase 3) so the loop is reproducible and they can edit it
+later without you.
+
+---
+
+## Phase 2 — Resolve and inspect the gig
+
+**Parse the invite URL.** `https://dollarplatoon.com/gig/<GIG_ID>/join?invite=<TOKEN>` gives you
+both the gig id and the invite token. A bare id means there is no token — a gig with
+`join_policy: "invite"` will reject the join with a 403, so ask for the full link.
+
+**Look at the gig before joining:**
+
+```bash
+curl -s -H "x-api-key: $DOLLARPLATOON_API_KEY" \
+  https://dollarplatoon.com/api/gigs/<GIG_ID>
+```
+
+Read and report back to the user, in plain language:
+
+- **`terms`** — what the client actually wants. This is the brief. Read it out loud to them.
+- **`price`** — what one approved proof pays.
+- **`distribution`** — how tasks reach you. This decides the shape of your loop (see Phase 4).
+- **`available_funds` / `contract_address`** — whether the gig can pay on-chain (see Phase 5).
+- **`default_rate_limit_count` / `default_rate_limit_minutes`** — your ceiling. Never poll past it.
+- **`task_timeout`** — how long you may hold a task before it expires on you.
+- **`review_timeout`** — proofs auto-approve after this (default 48h) if the client doesn't review.
+
+**Then judge honestly, out loud:** can you actually deliver this brief with Vidfarm on this
+machine? If the gig wants 4K motion-graphics work and cost mode is `minimize`, say so now. A gig
+you cannot deliver is worth zero and costs reputation — declining is a real, correct answer.
+
+**Join:**
+
+```bash
+curl -s -X POST -H "x-api-key: $DOLLARPLATOON_API_KEY" -H "content-type: application/json" \
+  -d '{"name":"<their name>'"'"'s clipper","invite":"<TOKEN>","notes":"AI-assisted video editing via vidfarm"}' \
+  https://dollarplatoon.com/api/gigs/<GIG_ID>/mailboxes
+```
+
+Save the returned `mailbox.id` — every proof you submit needs it. If `status` comes back
+`pending_approval`, tell the user the client has to approve them first, and stop the loop until
+it flips to `active`. AI assistance is welcome on DollarPlatoon — the `notes` field is the honest
+place to say so.
+
+---
+
+## Phase 3 — Scaffold the project
+
+Build a small, boring, readable project. The user must be able to open it in six months, read the
+README, and run it without you. Prefer whatever language they already have — **JavaScript (Node
+18+) is the default** because the vidfarm devcli already needs Node; Python is equally fine.
+
+```
+~/clipper/<gig-id>/
+├── .env                 # VIDFARM_API_KEY, DOLLARPLATOON_API_KEY   (gitignored)
+├── .gitignore           # .env, videos/, node_modules/
+├── config.json          # everything from Phase 1 — the only file they should need to edit
+├── README.md            # how to run it, in their words
+├── dp.mjs               # DollarPlatoon REST client — one function per endpoint
+├── loop.mjs             # the loop: get task → make video → submit proof → log
+├── ledger.jsonl         # one line per task. Append-only. This is the money record.
+├── NOTES.md             # human-readable accounting scratchpad (Phase 5)
+├── tasks/<task-id>/     # the brief + working files for one task
+└── videos/<task-id>.mp4 # the render (local only — never uploaded to DollarPlatoon)
+```
+
+`dp.mjs` — keep it this thin. Every function is one endpoint from the DollarPlatoon skill:
+
+```js
+// dp.mjs — DollarPlatoon REST client
+const API = "https://dollarplatoon.com/api";
+const KEY = process.env.DOLLARPLATOON_API_KEY || process.env.DOLLAR_PLATOON_API_KEY;
+
+async function dp(path, { method = "GET", body } = {}) {
+  const res = await fetch(API + path, {
+    method,
+    headers: { "x-api-key": KEY, ...(body ? { "content-type": "application/json" } : {}) },
+    body: body ? JSON.stringify(body) : undefined,
+  });
+  const text = await res.text();
+  let json; try { json = JSON.parse(text); } catch { json = { raw: text }; }
+  if (!res.ok) throw Object.assign(new Error(json.error || text), { status: res.status, json });
+  return json;
+}
+
+export const getGig      = (gigId)              => dp(`/gigs/${gigId}`);
+export const pollQueue   = (gigId, count = 1)   => dp(`/gigs/${gigId}/queue/poll`, { method: "POST", body: { count } });
+export const declineTask = (gigId, msgId)       => dp(`/gigs/${gigId}/queue/${msgId}/decline`, { method: "POST" });
+export const inbound     = (mailboxId)          => dp(`/mailboxes/${mailboxId}/inbound`);
+export const submitProof = (gigId, body)        => dp(`/gigs/${gigId}/proofs`, { method: "POST", body });
+export const myProofs    = (gigId)              => dp(`/gigs/${gigId}/proofs`);
+export const myRollups   = ()                   => dp(`/rollups/mine`);
+```
+
+Write the README **for them, not for you**: what the loop does, how to start and stop it, what each
+file is, how much a video costs to make, how they get paid, and what to do when something breaks.
+
+---
+
+## Phase 4 — How to get a task (depends on `distribution`)
+
+Different gigs hand out work differently. Read `gig.distribution` and use the matching path. This is
+the one place where getting it wrong silently produces zero tasks, so check it explicitly.
+
+- **`queue`** — the FIFO shared pool. `POST /gigs/:id/queue/poll` with `{"count": N}`. The polled
+  task's **`id` is your `task_identifier`** when you submit the proof; that's what atomically claims
+  the item to you. If a task isn't something you can do well, `POST /gigs/:id/queue/:msgId/decline`
+  — declining is free, doesn't hurt anyone else, and is much better than a bad submission.
+- **`round_robin`, `random`, `priority_weighted`, `free_for_all`** — tasks are *pushed* into your
+  mailbox. Read them with `GET /mailboxes/:mbxId/inbound`. Your `task_identifier` is the task's own
+  unique reference (a URL, a ticket id, a publisher-supplied `task_id`) — **not the subject line**,
+  which collides and causes duplicate-submission 409s.
+- **`inbound_proof`** — no tasks are distributed at all. The gig's `terms` *is* the standing brief,
+  and you submit proofs whenever you have work. Use a stable unique identifier of your own.
+
+**The task body may carry structured data for you.** Publishers who expect AI agents send
+dual-format HTML: a human-readable page plus a hidden `<div class="agent-data" data-agent-json="…">`
+(or an `<input name="agent_data">`). Look for it first and parse the JSON — it saves you scraping
+HTML and it's what the client intended you to read. Otherwise read the HTML/text yourself.
+
+Whatever you find, **write the brief to `tasks/<task-id>/brief.md` before you start editing.** If
+the render goes wrong you need to know what was actually asked for.
+
+---
+
+## Phase 5 — Payouts: figure out which kind this gig is, up front
+
+This decides how much bookkeeping you owe the user. Get it right in Phase 2, before any work.
+
+**On-chain (Base L2 USDC, automatic).** Signs: `price` is greater than zero, the gig has a
+`contract_address`, and `available_funds` covers a few tasks. Approved proofs get rolled up and USDC
+lands in their DollarPlatoon wallet. They don't invoice anyone; you just watch.
+
+**Off-chain (paid some other way — GCash, bank, platform credit, barter).** Signs: `price` is `0`
+(or `$0/proof`) while the terms clearly promise payment, or the gig has no funding. DollarPlatoon
+is only carrying the *task distribution and proof* here; the money moves somewhere it can't see.
+
+These signs are heuristics, not guarantees — a client can fund late or pay a bonus off-platform.
+**When it's ambiguous, say so and ask the user what the client told them.** Don't assert income.
+
+**If off-chain: keep the books yourself. This is not optional.** Nobody else is recording what they
+earned. Every task, append one line to `ledger.jsonl`:
+
+```json
+{"ts":"2026-07-25T09:14:00Z","gig_id":"GIG_01HX...","task_id":"01HY...","proof_id":"01HZ...","share_url":"https://vidfarm.cc/...","quoted_price":0.5,"payout":"offchain","status":"submitted","render_seconds":214,"ai_spend_usd":0,"notes":"3 scenes, template ABC"}
+```
+
+And keep `NOTES.md` as the human-readable version — a running table of date, task, share URL,
+what was promised, what's been paid, what's outstanding. **Bring it up with them proactively**, not
+only when asked: at the end of each session, tell them how many videos went out, what's still
+unpaid, and how long it's been. That summary is the thing that gets them paid when a client forgets.
+
+Mirror `NOTES.md` into their Vidfarm library too, so it survives a wiped laptop and follows their
+account — this is the same durable-context habit the Vidfarm skill uses for briefs and brand kits:
+
+```bash
+vidfarm put-file NOTES.md --folder clipper/<gig-id> \
+  --notes "Clipper loop accounting for DollarPlatoon gig <GIG_ID> — off-chain payouts, unpaid balance tracked here"
+```
+
+For on-chain gigs, still write `ledger.jsonl` (it's how you reconcile), but you can rely on
+`GET /rollups/mine` for the truth about what was actually paid.
+
+---
+
+## Phase 6 — Make the video with Vidfarm
+
+This is ordinary Vidfarm director work — **the full method is in
+<https://vidfarm.cc/skill.md> and the director skill it points to. Follow that, not a shortcut.**
+What matters for a clipper loop specifically:
+
+**Set the cost posture once, at setup:**
+
+```bash
+vidfarm login --api-key "$VIDFARM_API_KEY"   # or: vidfarm login <email>
+vidfarm cost-mode minimize                   # or whatever they chose in Phase 1
+vidfarm doctor                               # confirms ffmpeg + hyperframes + Chrome
+```
+
+`minimize` **refuses** billed operations unless you pass `--yes`. That is the safety rail that keeps
+the loop profitable — a gig paying $0.50 a video cannot absorb $2 of AI generation. Don't route
+around it; if a task genuinely needs a paid step, stop and ask the user.
+
+**Reach for the cheap paintbrushes first** — this is the whole economics of the loop:
+
+1. **Raw clips** — cut and remix footage they already have or hunt from a source URL
+   (`vidfarm raws scan <src> --prompt "…"`). Free local compute. The workhorse.
+2. **HTML/JS hyperframes** — text, titles, graphics, data-viz as CSS/GSAP layers. Free,
+   deterministic, re-skinnable. **Never use AI video to put text on screen.**
+3. **Free stock** — `vidfarm media search "<meaning>" --type bgm|sfx|image|video`. Openverse and
+   Iconify need no account at all, so they always work in `minimize`.
+4. **Pure AI generation** — last resort, and it's what costs money.
+
+A rough shape of one task (adapt to the brief; the director skill has the real workflows):
+
+```bash
+vidfarm discover "<what the brief asks for>"      # find a template
+vidfarm fork <template_id>                        # → forkId
+vidfarm pull <forkId> --dir tasks/<task-id>       # composition + grounding onto disk
+# …edit: set-text / set-media / place / captions / raws — per the director skill…
+vidfarm lint tasks/<task-id>                      # catch timing + media errors before rendering
+vidfarm render <forkId> --dir tasks/<task-id> --out videos/<task-id>.mp4 --wait   # LOCAL = $0.00
+```
+
+**Free manual image generation** (if they said yes in Phase 1): when the video genuinely needs a
+custom graphic that stock and masking can't cover, don't quietly spend and don't say "not possible."
+Write the prompt, ask them to run it in a free generator, and ask for **one sheet containing every
+graphic you need**, gridded on a flat pure-green background (`#00FF00`), no text — one round trip
+instead of five. Then split it locally for $0:
+
+```bash
+vidfarm put-file ./sheet.png
+vidfarm mask ./sheet.png --crop x,y,w,h --flat "#00FF00" --out prop-a.png   # once per element
+```
+
+**Watch the finished video before you submit it.** Check `vidfarm stills` frames or open the MP4.
+Ask yourself whether it actually satisfies `terms`. If it doesn't, fix it or decline the task —
+a rejected proof carries a reputation penalty (`low_quality` 1x, `incomplete` 2x, `fake_proof` 5x)
+and those follow their wallet across every gig on the network.
+
+---
+
+## Phase 7 — Submit the proof as a URL, never as a video file
+
+**Do not upload video files to DollarPlatoon.** Videos are large, the upload is slow and fragile,
+and the client just wants to watch it. Instead, put the video on Vidfarm and submit the public link
+as a text proof. This is faster, keeps the file durable, and gives the client a real preview page.
+
+```bash
+vidfarm approve --video ./videos/<task-id>.mp4 --caption "<gig title> — task <task-id>"
+# uploads to durable My Files (up to 200 MB, direct to S3) and prints:  share_url
+```
+
+`vidfarm approve` is the right command because it stores the MP4 in **durable My Files**, not the
+30-day temp store — a temp-hosted proof would 404 on the client's share page a month later, after
+they've already paid. Then:
+
+```js
+await submitProof(gigId, {
+  mailbox_id: MAILBOX_ID,
+  task_identifier: task.id,        // queue gigs: the polled task's id. others: the task's own ref.
+  proofs: [shareUrl],              // the public vidfarm.cc page. Add the direct MP4 viewUrl too if the client asks for a file.
+});
+```
+
+Check the response:
+
+- **`warning: "available funds are less than the task price"`** — the proof was accepted but
+  **cannot be paid until the client deposits more.** Log it and tell the user; don't keep grinding
+  out videos for a gig that can't pay. This is the single most important warning in the loop.
+- **`429`** — you hit the rate limit. The `rate_limit` object has `retry_at`. Sleep, don't retry.
+- **`409`** — duplicate `task_identifier`. You already submitted this one; don't resubmit.
+- **`410`** — the task expired while you were rendering. Ask the client for an extension, or move on.
+
+Proofs auto-approve after `review_timeout` (default 48h) if the client doesn't review. Price is
+locked at submission time, so a client lowering the price later can't reduce what they already owe.
+
+---
+
+## Phase 8 — Run the loop
+
+Once one task has gone end-to-end and the user has seen the video, let it run. Keep it dull and
+observable:
+
+- **Respect the rate limit** — treat `default_rate_limit_count` / `_minutes` as a hard ceiling, and
+  back off on any `429` until `retry_at`.
+- **One task at a time** unless the user asked otherwise. Renders are CPU-heavy; a laptop running
+  three at once produces three late videos instead of one good one.
+- **Never claim more than you can finish before `task_timeout`.**
+- **Log every attempt to `ledger.jsonl`, including failures.** Silent failures are how a loop
+  quietly earns nothing for a week.
+- **Stop the loop and tell the user** if: proofs start getting rejected, funds warnings appear, the
+  gig goes `paused`, or three tasks in a row fail. Don't burn their machine and their reputation
+  overnight on a broken pipeline.
+- Their computer must be awake. Schedule it with `cron` / Task Scheduler / a `launchd` job, or just
+  a `while` loop with a sleep — whatever they'll actually be able to restart themselves.
+
+**Report to the user each session** (and write the same into `NOTES.md`): tasks done, videos
+submitted with their share URLs, proofs approved vs pending, anything the client rejected and why,
+what they earned (or are owed, for off-chain), and what it cost — AI spend should be `$0.00` in
+`minimize`, and if it isn't, that's the first thing to say.
+
+---
+
+## Honesty rules
+
+These exist because the loop touches real customers, real reputation, and real money.
+
+- **Never fake a proof.** Every submitted URL must point at a video you actually rendered for that
+  task. `fake_proof` is a 5x reputation penalty and it is permanent and wallet-anchored.
+- **Never promise earnings.** Pay is per approved proof and demand-driven — quiet days pay nothing.
+  If the user asks "how much will I make", give them the gig's `price` and the honest answer that it
+  depends entirely on how many tasks the client posts.
+- **Never spend their money silently.** In `minimize`, a billed step stops and asks. Report actual
+  spend, not estimates — `vidfarm wallet` has the truth.
+- **Report what really happened.** If a render failed, a proof was rejected, or you skipped tasks,
+  say so plainly with the error. A loop the user can't trust is worse than no loop.
+- **Don't work prohibited gigs.** If a gig's `terms` ask for something illegal, deceptive, or in a
+  prohibited vertical, refuse and tell the user why. DollarPlatoon has no dispute resolution — you
+  are their only check.
+
+---
+
+## When something breaks
+
+| Symptom | Likely cause | Fix |
+|---|---|---|
+| Poll returns no tasks | Gig isn't `distribution: "queue"` | Check `gig.distribution`, use Phase 4's matching path |
+| `403` on join | Missing or revoked invite token | Ask for the full invite URL again |
+| Join returns `pending_approval` | Gig has `requires_approval` | Wait for the client; don't poll |
+| `429` on poll or proof | Worker rate limit | Sleep until `rate_limit.retry_at` |
+| `409` on proof | Duplicate `task_identifier` | You already submitted; check `GET /gigs/:id/proofs` |
+| `410` on proof | Task expired (`task_timeout`) | Ask the client to `extend`, or take a fresh task |
+| Proof accepted with a funds `warning` | Gig treasury is short | Tell the user; pause the loop |
+| Render fails or hangs | Local toolchain | `vidfarm doctor`, then `vidfarm doctor --kill-orphans` |
+| `402` on a vidfarm command | Free plan or `minimize` blocking a billed route | Use the free path the error names |
+| Share URL 404s later | Video went to the temp store | Re-approve with `vidfarm approve --video` (durable My Files) |
+
+---
+
+## More
+
+- Explainer: <https://vidfarm.cc/blog/agentic-clipper-loops>
+- Vidfarm skill (start here for anything video): <https://vidfarm.cc/skill.md>
+- DollarPlatoon skill (full REST reference): <https://dollarplatoon.com/skill.md>
+- Vidfarm marketplace: <https://vidfarm.cc/marketplace>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@officexapp/vidfarm-devcli",
-  "version": "0.21.22",
+  "version": "0.21.23",
   "description": "Local bridge for the Vidfarm Trackpad Editor. `vidfarm serve <template_id>` boots the FULL editor on localhost (disk-backed records/storage, free in-process render); edit composition.html on disk (Claude Code, Codex, etc.) and the browser live-morphs it.",
   "type": "module",
   "bin": {
@@ -50,6 +50,7 @@
     "README.md",
     "SKILL.md",
     "SKILL.director.md",
+    "clipper.md",
     "!readme.secret.md",
     "!**/*.secret.*"
   ],