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-interviewgit 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-interview)<a href="https://agentmods.dev/skills/mrdesign-ww/vault-os/seedance-interview"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/seedance-interview/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-interview"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/seedance-interview.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.00068 | $0.03343 |
| Opus 5 | $0.00034 | $0.01672 |
| Sonnet 5 | $0.00014 | $0.00669 |
| Haiku 4.5 | $0.00007 | $0.00334 |
Grade A, and why
seedance-interview 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
86% identical to seedance-interview — 64 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seedance-interview
The front door - and three different people walk through it. The same questions do not serve all three:
- someone with no idea yet, carrying only a feeling and no words for it;
- someone with a rough idea they can half-describe;
- a professional who already thinks in shots, lenses, blocking, and performance.
Read which one is in front of you before asking anything. The baseline assumption is still no film background - every plain question must be answerable by someone who has never heard the words "shot," "aspect ratio," or "blocking" - but never ask a question the person cannot answer, and never flatten someone who already knows exactly what they want.
Start Where They Are
No idea yet - do not interrogate. A blank-slate user cannot answer "who is the star?" because they have not decided yet; asking is exactly what makes the tool feel unfriendly. Lead with something to react to instead of a question to answer: offer the Starting Points menu below, or draft one complete concept from whatever scrap they gave and invite a reaction. "I don't know" and "surprise me" are complete answers - they select a proposal, never a stall.
Rough idea - run the plain Priority Question Pool, skipping every question the idea already answers, and propose the mini-treatment as early as one round in, or zero rounds if the idea is already rich.
Professional - the moment the user gives, or offers to give, explicit shot size, lens, camera move, blocking, or performance direction, switch to a precise intake in their own vocabulary. Load [ref:pro-filmmaking-standards] and [ref:cinematography-shot-language], capture their direction verbatim, fill only the gaps they left, and never translate their craft into plain words or re-decide what they already decided.
When the level is unclear, let them choose rather than guessing: "I can keep this simple - or, if you already think in shots and lenses, tell me and I'll skip straight to a precise spec."
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 · 141 lines · 68 tokens per session scan A 89dd670c284c
seedance-interview is a skill published in the GitHub repository mrDesign-ww/vault-os (2 stars, last pushed 3d ago), licensed MIT. It adds 68 tokens to every session and 3,343 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to seedance-interview, differing in 64 lines, and is treated as a copy.
Other skills, from other repositories
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-interview
This skill should be used when the user has a vague Seedance 2.0 video idea and asks for creative guidance, story development, scene planning, a director interview, or help turning an undeveloped concept into a production-ready prompt, especially when the user has no film or storytelling background.
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-interview-short
This skill should be used when the user wants a fast Seedance 2.0 creative brief, a short interview, a compressed intake flow, or a quick director-style clarification before prompt writing.
seedance-interview-short
This skill should be used when the user wants a fast Seedance 2.0 creative brief, a short interview, a compressed intake flow, or a quick director-style clarification before prompt writing.
seedance-interview-short
This skill should be used when the user wants a fast Seedance 2.0 creative brief, a short interview, a compressed intake flow, or a quick director-style clarification before prompt writing.