What is handle-limits-and-errors?

A guide for responding to structured Vivideo API errors, including rate limits, missing credits, plan restrictions, duplicate requests, and invalid settings.

Use it to follow retry delays, read allowed values, handle duplicate jobs, provide account links, and retain the request ID for support.

It separates errors that can be retried from those that require a user action, such as upgrading or buying credits.

handle-limits-and-errors — Skill by egocen-vivideo/vivideo-toolchain

Install

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.

Any agent

npx skills add egocen-vivideo/vivideo-toolchain --skill handle-limits-and-errors

Clone the repo

git clone --depth 1 https://github.com/egocen-vivideo/vivideo-toolchain

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/egocen-vivideo/vivideo-toolchain/handle-limits-and-errors/github.svg)](https://agentmods.dev/skills/egocen-vivideo/vivideo-toolchain/handle-limits-and-errors)

Your own site

<a href="https://agentmods.dev/skills/egocen-vivideo/vivideo-toolchain/handle-limits-and-errors"><img src="https://agentmods.dev/badge/skills/egocen-vivideo/vivideo-toolchain/handle-limits-and-errors/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/egocen-vivideo/vivideo-toolchain/handle-limits-and-errors"><img src="https://agentmods.dev/badge/skills/egocen-vivideo/vivideo-toolchain/handle-limits-and-errors.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 655 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00040	$0.00655
Opus 5.5	$0.00016	$0.00262
Sonnet 5.5	$0.00008	$0.00131
Haiku 4.5	$0.00004	$0.00065

Measured 2mo ago against content hash 00ec62e3d6ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

handle-limits-and-errors 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.

skills/handle-limits-and-errors/SKILL.md · 42 lines

How it starts

The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Handle Vivideo errors, limits & retries

Every Vivideo error is structured: { error: { code, kind, message, retryable, request_id, retry_after_seconds?, details?, links? } }. Branch on code/kind, never on message text. Keep request_id for support.

By kind

rate_limited (HTTP 429) — you're sending too fast.
- Wait retry_after_seconds, then retry the same request. The client already backs off, but if you see this, slow your own loop down. Don't fan out parallel calls.
insufficient_credits (402) — not enough credits.
- Not retryable. Tell the user to buy credits at links.buy_credits. Don't retry the create.
upgrade_required / free_limit_reached (403) — needs a premium plan (or the one free video is used).
- Not retryable. Give links.upgrade. A free account's create returns a preview instead of rendering — see render_preview after they upgrade.
duplicate (duplicate_request / idempotency_in_flight, 409) — an identical create is already in flight.
- Don't create again. Use the existing video (details.existing_video_id if present) or wait and check status. Send an idempotency_key to make retries safe — see avoiding-duplicate-generations.
invalid_request (400, incl. unknown_model, invalid_url) — bad input.
- Not retryable as-is. Read details.allowed / details.field and fix the input, then retry once with a valid value.
auth (401) — missing/invalid/revoked key.
- Not retryable. Ask the user to set a valid VIVIDEO_API_KEY / run vivideo configure.
server (5xx / upstream_error) and network (timeout) — transient.
- Retryable with backoff. The client retries a bounded number of times automatically; if it still fails, tell the user and keep the request_id.

Retry rules

Retry only when retryable: true (rate_limited, server, network).
Honor retry_after_seconds on 429.
Bounded attempts + exponential backoff (the client does this; don't add your own tight retry loop on top).
Never retry insufficient_credits, upgrade_required, auth, or an unchanged invalid_request.

Read the full file on GitHub · 42 lines

Changes

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 · 42 lines · 40 tokens per session scan A 00ec62e3d6ab

Subscribe to this mod's changes

handle-limits-and-errors is a skill published in the GitHub repository egocen-vivideo/vivideo-toolchain (0 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 655 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.

handle-limits-and-errors next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
handle-limits-and-errorsegocen-vivideo/vivideo-toolchain	Skill	0	3mo ago	MIT	A	40	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