Skip to content

frankxai/creator-skills / skills/video/video-engine-routing

video-engine-routing

Verified

Decide WHERE video/image generation runs when cost, volume, or capability forces a choice - subscription credits vs pay-per-use APIs vs cloud ComfyUI. Use when asked "which video engine should I use", "is Higgsfield/fal/RunComfy worth it", "credits ran out", "cheapest way to generate N clips", "do I need ComfyUI", "should I run this locally", or when the video-gen skill escalates a budget or capability ceiling. Contains the pricing table, graduation triggers, and the never-local rule for iGPU machines.

video-engine-routing — when you outgrow your default engine

The default stack (see video-gen) assumes a subscription engine. This skill is the escalation path: what to do when credits run out, volume grows, or the pipeline needs control the subscription engine cannot give.

The decision tree

  1. Under ~50 clips/month, mixed styles, no custom pipeline → stay on the subscription engine you already pay for (an all-in-one such as Higgsfield, or an equivalent). Sunk cost, routing across many models, zero ops.
  2. Bursty overflow or budget clips at volume → pay-per-use API (fal.ai). No subscription, no credit expiry, cheapest per-clip for budget models.
  3. Custom pipeline: LoRA character consistency at batch scale, ControlNet/IPAdapter chains, motion transfer, community models → cloud ComfyUI (RunComfy machines or Comfy Cloud). You are paying for control, not per-clip price.
  4. Local GPU rendering → only with a recent NVIDIA card with 16 GB+ VRAM. On an iGPU machine (Intel Arc/AMD APU, shared memory): never. Modern video models blow through shared-memory budgets, and quantized variants degrade video coherence. Cloud is faster and cheaper than wasted local hours.

Pricing reference (mid-2026, one 5-second 1080p clip)

These are the author's working estimates, not vendor quotes, and none is sourced here. Open each vendor's current pricing page before you decide.

RouteCost per 5s clipNotes
All-in-one subscription (Higgsfield)~$0.30–0.50 in creditstiers $15–129/mo; credits don't roll over
fal.ai — Seedance 2.0 Fast~$0.11cheapest respectable social clip
fal.ai — Kling~$0.35pay-per-second, no minimums
fal.ai — Veo 3.1 Fast~$0.50 (720p)4K tier ~3×
RunComfy machines$0.99–9.59/hr + Pro $20/mocustom ComfyUI workflows; cold-start overhead makes single clips uneconomic
Comfy Cloud$20/mo ≈ 180 GPU-minofficial ComfyUI cloud, credit-based
ComfyDeploy—defunct; stack was open-sourced, managed service gone

Recompute before deciding: prices move quarterly. The structure (subscription vs per-use vs machine-rental) is what stays stable.

Graduation triggers

  • To fal.ai: monthly credit top-ups exceed ~$20 two months running, or you need one premium model your subscription lacks.
  • To cloud ComfyUI: you need the same character across 10+ videos via LoRA, or a ControlNet/IPAdapter/motion-control chain no API engine exposes, or 100+ clips/month of one repeatable workflow where machine-hours beat per-clip pricing.
  • Back down: if a rented workflow runs less than monthly, cancel the machine and take the per-use price. Idle infrastructure is the most expensive engine.

What not to do

  • Don't install vendor API-wrapper skill packs for engines you don't pay for — every one of them is lock-in to that vendor's endpoint with no portable workflow definition.
  • Don't run modern video models on integrated GPUs (see rule 4 above).
  • Don't hold two overlapping subscriptions to hedge; pick one default and use per-use APIs as the hedge.

Credits

The single-dispatcher/model-leaf routing pattern used by video-gen is adapted from the router design in agentspace-so's RunComfy skill pack — pattern absorbed, dependency skipped.

Disclosure: the author is a Higgsfield Ambassador, and Higgsfield links on frankx.ai may be affiliate links. The routing logic here does not depend on that relationship: the decision tree sends you to fal.ai or ComfyUI whenever those genuinely win.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall