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 wait-for-video-safelygit 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/wait-for-video-safely)<a href="https://agentmods.dev/skills/egocen-vivideo/vivideo-toolchain/wait-for-video-safely"><img src="https://agentmods.dev/badge/skills/egocen-vivideo/vivideo-toolchain/wait-for-video-safely/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/wait-for-video-safely"><img src="https://agentmods.dev/badge/skills/egocen-vivideo/vivideo-toolchain/wait-for-video-safely.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.00046 | $0.00419 |
| Opus 5.5 | $0.00018 | $0.00168 |
| Sonnet 5.5 | $0.00009 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
wait-for-video-safely 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 2mo 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
Wait for a video safely (polling vs webhooks)
Renders take seconds to a few minutes. Waiting badly (tight loops, no timeout) turns into a request flood and can hang an agent. Do it safely.
Preferred: wait_for_video
- Call
wait_for_videowith the videoidand atimeout_seconds(e.g. 300). - It polls at the API's suggested
poll_interval_seconds(never faster), up to the timeout. - It returns
{ timed_out, video }:timed_out: false→video.statusis terminal (completed/failed/preview). Act on it.timed_out: true→ still rendering. Hand control back to the user ("still processing, I'll check again shortly") and callwait_for_video/get_videoagain later. Don't busy-wait.
If you must poll manually (get_video)
- Respect
poll_interval_secondsfrom the response between calls. - Cap total attempts / total time. Never
while(true). - Treat
completed,failed, andpreviewas stop conditions.
Webhooks (for backends, not interactive agents)
- For a server that can receive HTTP, register a webhook (
POST /v1/webhooks) and get a signedvideo.completed/video.failedevent instead of polling. - Use polling for interactive/agent flows; use webhooks for long-running backends.
Never
- ❌ Never say the video is "done"/"ready" until the API returns
status: "completed". - ❌ Never poll faster than
poll_interval_seconds. - ❌ Never block indefinitely — always have a timeout.
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.
- 2mo ago First seen · 30 lines · 46 tokens per session scan A f483b16fb2df
wait-for-video-safely is a skill published in the GitHub repository egocen-vivideo/vivideo-toolchain (0 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 419 once invoked, about $0.0002 per session on Opus 5.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.
wait-for-video-safely compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| wait-for-video-safelyegocen-vivideo/vivideo-toolchain | Skill | 0 | 3mo ago | MIT | A | 46 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | yesterday | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 315k | 5d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |