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 skills add egocen-vivideo/vivideo-toolchain --skill create-manual-videogit clone --depth 1 https://github.com/egocen-vivideo/vivideo-toolchainWrote 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/egocen-vivideo/vivideo-toolchain/create-manual-video)<a href="https://agentmods.dev/skills/egocen-vivideo/vivideo-toolchain/create-manual-video"><img src="https://agentmods.dev/badge/skills/egocen-vivideo/vivideo-toolchain/create-manual-video/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/egocen-vivideo/vivideo-toolchain/create-manual-video"><img src="https://agentmods.dev/badge/skills/egocen-vivideo/vivideo-toolchain/create-manual-video.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00057 | $0.00483 |
| Opus 5 | $0.00028 | $0.00242 |
| Sonnet 5 | $0.00011 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
create-manual-video 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 11d 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.
What it actually says
Create a manual-mode video
Manual mode sends your prompt straight to one model. Use it when the user picks a model or needs image-to-video.
Workflow
check_configuration→check_account(premium + credits).- Choose a model and read its options. Call
list_modelswithmode: "manual". Each model lists exactly what it accepts:operations(text_to_video, image_to_video, first_last_frame, multiple_images)durations,resolutions,aspect_ratios,stylescredits_per_second(forestimate_credits) Only use values from that model's lists. An invalidresolution/duration_seconds/aspect_ratio/stylereturns a400 invalid_requestwhosedetails.allowedlists the valid values — read it and retry with a valid value.
- (Optional) estimate with
estimate_credits(mode: "manual", themodel,duration_seconds,resolution). - Create with
create_manual_video:model,prompt, and the validatedduration_seconds/resolution/aspect_ratio.- The operation is inferred from inputs: add
image_url(public https) for image-to-video. Don't pass anoperationfield — it doesn't exist.
- The operation is inferred from inputs: add
- Wait with
wait_for_video; returnvideo_urlwhencompleted.
Rules
- Manual mode has no avatar/voice/brand-kit — those are auto-mode only.
image_urlmust be a public https URL. If the user has a local file, upload it first (POST /v1/uploads→ use the returnedpublic_url).- On
400 invalid_request, fix the field named indetailsand retry — do not keep sending the same invalid value. - Follow
generate-video-from-promptfor wait/result/error mechanics.
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.
- 11d ago First seen · 27 lines · 57 tokens per session scan A f9a1681b15ab
create-manual-video is a skill published in the GitHub repository egocen-vivideo/vivideo-toolchain (0 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 483 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…