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 sideshowroberto/vfx-agent-toolkit --skill seedance-pipelinegit clone --depth 1 https://github.com/sideshowroberto/vfx-agent-toolkitWrote 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/sideshowroberto/vfx-agent-toolkit/seedance-pipeline)<a href="https://agentmods.dev/skills/sideshowroberto/vfx-agent-toolkit/seedance-pipeline"><img src="https://agentmods.dev/badge/skills/sideshowroberto/vfx-agent-toolkit/seedance-pipeline/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/sideshowroberto/vfx-agent-toolkit/seedance-pipeline"><img src="https://agentmods.dev/badge/skills/sideshowroberto/vfx-agent-toolkit/seedance-pipeline.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.00055 | $0.00696 |
| Opus 5.5 | $0.00022 | $0.00278 |
| Sonnet 5.5 | $0.00011 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
seedance-pipeline 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 today.
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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seedance-pipeline
Reference resolution: [ref:<name>] resolves to ../seedance-20/references/<name>.md (the seedance-20 skill's vendored reference corpus); [skill:<name>] is the sibling skill of that name.
Use this for operational workflows, APIs, web surfaces, post-production, and integration planning.
Status Rule
Always load [ref:api-status] for current API and platform claims. Load [ref:model-name-map] when a user says Pro, Fast, V2, or a wrapper model ID. Do not rely on old release-status memory.
Load [ref:api-workflow] for implementation planning, task lifecycle, Runway/Volcengine field differences, pricing caveats, upload handling, and production readiness.
Load [ref:pro-filmmaking-standards] for professional film, commercial, agency, localization, post, and delivery workflows. Load [ref:delivery-qc] before saying an asset is delivery-ready.
Workflow Split
- Web workflow: Dreamina/Jimeng surface, references, prompt, output review.
- API workflow: Volcengine, BytePlus, or Runway docs, model ID, auth, file handling, task creation, polling/querying, cancellation/deletion, task ledger, and retrieval.
- Professional production workflow: treatment, shot list, continuity ledger, reference rights map, review loop, post handoff, and delivery/QC.
- Post workflow: edit, conform, stitching, stabilization, audio cleanup, captions/subtitles, color, localization, versioning, textless, and delivery.
- First/last-frame workflow: map first frame, last frame, transition action, identity locks, and ending target.
- Runway workflow: model
seedance2,runway://uploads, audio-reference combination rules, plan/region caveats, and SDK type lag are Runway-specific. - Community workflow: ComfyUI or unofficial nodes must be labeled community/unverified unless sourced.
- Corpus-mining workflow: classify sources before reuse; extract structure and vocabulary, not unsafe raw prompts.
Output Contract
Return the workflow path, source status, required inputs, production phase, validation steps, delivery assumptions, and risks. For professional jobs, include the next artifact to create: brief, shot list, continuity ledger, prompt batch, review packet, localization matrix, or QC preflight.
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.
- today First seen · 48 lines · 55 tokens per session scan A 16dd819d0b1f
seedance-pipeline is a skill published in the GitHub repository sideshowroberto/vfx-agent-toolkit (16 stars, last pushed 22d ago), licensed MIT. It adds 55 tokens to every session and 696 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-11-02.
Other skills, from other repositories
seedance-pipeline
This skill should be used when the user asks about Seedance 2.0 workflow operations, API planning, BytePlus ModelArk, Dreamina/Jimeng surfaces, provider/router APIs, China-facing surfaces, ComfyUI, post-production, stitching, batch workflow, or integration planning.
flowise-builder
Use when flowise visual LLM workflow builder — drag-drop chatflows, API endpoints, document loaders, tools. Use when working with flowise builder.
postbridge-social-manager
Use when multi-platform social media posting, scheduling, analytics, and media management via PostBridge API for TikTok, Instagram, X, LinkedIn, and Facebook. Use when working with postbridge social manager.
seedance-pipeline
This skill should be used when the user asks about Seedance 2.0 workflow operations, API planning, BytePlus ModelArk, Dreamina/Jimeng surfaces, provider/router APIs, China-facing surfaces, ComfyUI, post-production, stitching, batch workflow, or integration planning.
ome-api
Integrate API clients, services, and contracts using project rules.
agent-creator
Create custom AI subagents with proper plugin structure, persona generation, and companion routing skills.