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 agentmods add skills/1370998960-del/https-github.com-emily2040-seedance-2.0/seedance-continuationnpx skills add 1370998960-del/https-github.com-Emily2040-seedance-2.0 --skill seedance-continuationgit 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-continuation)<a href="https://agentmods.dev/skills/1370998960-del/https-github.com-emily2040-seedance-2.0/seedance-continuation"><img src="https://agentmods.dev/badge/skills/1370998960-del/https-github.com-emily2040-seedance-2.0/seedance-continuation.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.00053 | $0.00953 |
| Opus 5 | $0.00026 | $0.00477 |
| Sonnet 5 | $0.00011 | $0.00191 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
seedance-continuation 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seedance-continuation
Use this for seamless continuation, intentional next shots, bridge clips, tail repair, and re-anchoring after drift. A continuation prompt must be grounded in accepted footage, not only in the old plan.
Load [ref:continuation-handoff], [ref:sequence-project-state], [ref:prompt-compiler], [ref:reference-transfer-contract], and [ref:continuity-qc]. Load [ref:failure-atlas] when the continuation failed or drift is visible. Load [ref:directing-engine] so the next clip inherits the project's directorial voice and its position on the long-form spine; the look never re-rolls between clips.
Intent
The user already made something they accepted, and now they are trusting the story to continue from exactly where it really landed - not where the plan hoped it would. The soul of this skill is fidelity to what actually happened: honor the accepted footage as the only truth, refuse to invent the bridge, and ask for the real ending rather than guess it. Continuity is a promise that the film the user already has will not be quietly contradicted.
Required Input Gate
Before writing any continuation prompt, require:
project_id;- current
clip_id; - valid
parent_clip_id; - full-story objective;
- final story outcome;
- next planned narrative job;
- accepted previous clip or accepted final frame;
observed_end_state;- continuity locks;
- inherited directorial voice and arc position;
- exact reference registry;
- active surface or conservative surface profile.
If the source is unavailable, say: "I have the story plan, but I do not have the actual ending of the previous generation. Upload the clip or its final frame, or describe exactly what is visible at the end. I should not invent the continuation state."
Do not hide this uncertainty by writing a speculative prompt.
Continuation Types
seamless_continuation: same shot, same geography, same open motion, same or motivated camera continuation, and accepted previous footage as the source.
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.
- 6d ago First seen · 86 lines · 53 tokens per session scan A 5c71673905ac
seedance-continuation 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 53 tokens to every session and 953 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-30.
Other skills, from other repositories
seedance-continuation
This skill should be used when a Seedance 2.0 user asks to continue, extend, make the next part, repair the tail, bridge between known frames, re-anchor drift, or create a successor prompt from accepted footage.
seedance-continuation
This skill should be used when a Seedance 2.0 user asks to continue, extend, make the next part, repair the tail, bridge between known frames, re-anchor drift, or create a successor prompt from accepted footage.
seedance-sequence
This skill should be used when a Seedance 2.0 request is a long story, connected set of clips, multi-generation scene, campaign sequence, dense storyboard, continuation-ready plan, or any idea that must be divided into stateful clips.
seedance-sequence
This skill should be used when a Seedance 2.0 request is a long story, connected set of clips, multi-generation scene, campaign sequence, dense storyboard, continuation-ready plan, or any idea that must be divided into stateful clips.
seedance-interview
This skill should be used when the user wants creative guidance, story development, scene planning, or a director interview to turn a Seedance 2.0 idea into a production-ready prompt - adapting to users who have no idea yet, a rough concept, or precise professional direction in shots, lenses, and blocking.
seedance-prompt
This skill should be used when the user asks to write, improve, translate, compress, or debug a Seedance 2.0 video prompt; mentions T2V, I2V, V2V, R2V, camera direction, prompt quality, or provides reference assets for a production-ready prompt.