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 1370998960-del/https-github.com-Emily2040-seedance-2.0 --skill seedance-pipelinegit clone --depth 1 https://github.com/1370998960-del/https-github.com-Emily2040-seedance-2.0Wrote 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/1370998960-del/https-github.com-emily2040-seedance-2.0/seedance-pipeline)<a href="https://agentmods.dev/skills/1370998960-del/https-github.com-emily2040-seedance-2.0/seedance-pipeline"><img src="https://agentmods.dev/badge/skills/1370998960-del/https-github.com-emily2040-seedance-2.0/seedance-pipeline.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.1 | $0.00063 | $0.00833 |
| Opus 5 | $0.00032 | $0.00417 |
| Sonnet 5 | $0.00013 | $0.00167 |
| Haiku 4.5 | $0.00006 | $0.00083 |
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 8d 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.
This is a copy
88% identical to seedance-pipeline — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seedance-pipeline
Use this for operational workflows, APIs, web surfaces, post-production, and integration planning.
Intent
Behind every API question is a person with a deadline, a budget, and something at stake on this working tomorrow. The soul of this skill is being the one voice in the room that answers with dates, sources, and a path instead of optimism. Reliability is the kindness this user needs.
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/provider 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, Runway, fal, or provider/router 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. - Provider/router workflow: EvoLink, OpenRouter, Kie.ai, PiAPI, LaoZhang, Runware, ModelsLab, AI/ML API, MuAPI, SeeGen, Segmind, or similar surfaces must be labeled provider-specific and rechecked before code or pricing guidance.
- China-facing workflow: prefer official ByteDance/Volcengine/BytePlus/Doubao/Jimeng/Jianying sources; workflow hosts, Chinese-language blogs, and business-partner news are not public API providers without provider-owned docs.
- 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.
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.
- 8d ago First seen · 52 lines · 63 tokens per session scan A a14b99ef21db
seedance-pipeline is a skill published in the GitHub repository 1370998960-del/https-github.com-Emily2040-seedance-2.0 (235 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 833 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to seedance-pipeline, differing in 10 lines, and is treated as a copy.
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.
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.
ad-creative
Create, iterate, and scale paid ad creative for Google Ads, Meta, LinkedIn, TikTok, and similar platforms. Use when generating headlines, descriptions, primary text, or large sets of ad variations for.
ai-studio-image
Geracao de imagens humanizadas via Google AI Studio (Gemini). Fotos realistas estilo influencer ou educacional com iluminacao natural e imperfeicoes sutis.
ve-terminal-mono
OpenDesign from the CLI: driving the full design workflow with the od command — scripted, composable, agent-ready. Built as a decision-grade AI literacy deck for developers, power users.