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.
npx agentmods add skills/vibeknow/cli/vibeknow-createnpx skills add vibeknow/cli --skill vibeknow-creategit clone --depth 1 https://github.com/vibeknow/cliWrote 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.
[](https://agentmods.dev/skills/vibeknow/cli/vibeknow-create)<a href="https://agentmods.dev/skills/vibeknow/cli/vibeknow-create"><img src="https://agentmods.dev/badge/skills/vibeknow/cli/vibeknow-create.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00047 | $0.06119 |
| Opus 5 | $0.00023 | $0.03060 |
| Sonnet 5 | $0.00009 | $0.01224 |
| Haiku 4.5 | $0.00005 | $0.00612 |
Grade A, and why
vibeknow-create 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 3d ago.
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.
How it starts
The opening of the file, as written. The whole thing — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibeknow-create
TRIGGER
- User wants to generate a video from a document, URL, or file
- Check video task status or wait for completion
- Download a rendered video
- List available voice templates
SKIP
- Document upload/status only (no video) → use vibeknow-doc
- Auth, profile, config, diagnostics → use vibeknow-core
Run Contract
Applies from the moment a run starts. Every rule here exists because breaking it costs the user money or loses a run that was still going.
Never run vibeknow create twice for the same request. A second
create is a second billed render, always — it never recovers or resumes
the first one. If you have lost the ids, run vibeknow jobs list, then
vibeknow video list. Only start over when the CLI has told you in so many
words that it is safe (resend_safe: true, see exit 6 below).
One process owns the stream. create and video wait already poll the
backend, print progress, and collect the result. Do not start a second
video status loop alongside a running one, and do not wrap the command in
your own poller.
Do not resend because it went quiet. A render takes minutes and the pipeline is legitimately silent through some of them. Slowness, an empty patch of output, and a tool call that timed out on your side are all compatible with a run that is about to succeed.
Never merge the streams. 2>&1 destroys the contract: stdout is the
result and stderr is everything else. Redirect them to separate files if
you need to keep them.
Do not use tail -n 20 as a cursor. Events arrive in bursts. Read
stderr from a saved offset, or you will silently skip whole stages.
A finished process is not a finished run. The shell returning, a background job ending, or a notification arriving tells you nothing about the task. Read the exit code and stdout.
Never invent an --confirm value or add --yes on your own initiative.
When the CLI hands back a spend decision it has stopped precisely because
the choice is not yours to make. Relay it and wait.
What ships with it
4 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.
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.
- 3d ago First seen · 439 lines · 47 tokens per session scan A 7f7d6b8d7190
vibeknow-create is a skill published in the GitHub repository vibeknow/cli (6 stars, last pushed 7d ago), licensed MIT. It adds 47 tokens to every session and 6,119 once invoked, about $0.0002 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-31.
Other skills, from other repositories
reseed-performance-baseline
Re-seed the HF performance-tracking baseline for an intentional runtime, dependency, environment-caused benchmark shift, or reviewed v2 calibration using one or more reviewed normalized performance JSONs. Use when performance CI fails because metrics such as latency, throughput, component time, or peak memory changed…
add-model
Manual /add-model workflow for implementing a FastVideo model or first-class component port after add-model-01-prep has staged reference code and weights. Organizes the port into numbered phases with conversion rules, component policies, parity gates, and handoff checks.
seed-ssim-references
Seed HF reference artefacts for a single newly-added SSIM test (pixel .mp4 for runtexttovideosimilaritytest-style tests, or latent .pt for runtexttolatentsimilaritytest-style tests). Runs the test on Modal L40S, downloads the generated artefacts via modal volume get, pauses for the user to verify (visual eyeball for…
reseed-ssim-references
Re-seed HF reference videos for a single existing SSIM test on Modal L40S. Always backs up current refs locally first, regenerates on Modal, pauses for the user to eyeball before-vs-after quality, then overwrites the targeted model subtree on FastVideo/ssim-reference-videos with --force. Use when an intentional code…
add-model-02-parity
Use during /add-model after reference/architecture study to scaffold and later activate local FastVideo component parity tests. Emphasizes early test creation, official-reference loading, standardized FastVideo loading, and non-skip handoff gates.
add-model-09-pipeline
Use during /add-model Phase 7 after all required component parity tests pass to define FastVideo pipeline wiring, configs, presets, registry entries, examples, smoke tests, and pipeline parity tests.