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 mrDesign-ww/vault-os --skill seedance-continuationgit clone --depth 1 https://github.com/mrDesign-ww/vault-osWrote 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/mrdesign-ww/vault-os/seedance-continuation)<a href="https://agentmods.dev/skills/mrdesign-ww/vault-os/seedance-continuation"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/seedance-continuation/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/mrdesign-ww/vault-os/seedance-continuation"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/seedance-continuation.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.00053 | $0.01202 |
| Opus 5 | $0.00026 | $0.00601 |
| Sonnet 5 | $0.00011 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
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 2d 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
100% identical to seedance-continuation — 0 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 — 95 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; scene_id, and whether the next clip stays inside the scene or crosses a scene boundary;- full-story objective;
- final story outcome;
- next planned narrative job;
- next clip
felt_intent- what the viewer should feel or notice; - 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 - python scripts/extract_last_frame.py <take> pulls the final frame locally - or describe exactly what is visible at the end. I should not invent the continuation state."
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.
- 2d ago First seen · 95 lines · 53 tokens per session scan A aa855aa046a2
seedance-continuation is a skill published in the GitHub repository mrDesign-ww/vault-os (2 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 1,202 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to seedance-continuation, differing in 0 lines, and is treated as a copy.
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-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-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.