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-interview-shortgit 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-short)<a href="https://agentmods.dev/skills/mrdesign-ww/vault-os/seedance-interview-short"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/seedance-interview-short/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-short"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/seedance-interview-short.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.00045 | $0.00919 |
| Opus 5 | $0.00023 | $0.00460 |
| Sonnet 5 | $0.00009 | $0.00184 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
seedance-interview-short 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
89% identical to seedance-interview-short — 6 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seedance-interview-short
Use this when speed matters more than exhaustive creative discovery. The goal is to turn a vague idea into a compact director brief with no more than three questions, then route to prompt writing.
Intent
The user here knows what they want and is asking you to respect their momentum. The soul of this skill is restraint: find the one missing piece that would sink the generation, ask only that, and get out of the way. Speed is the form their trust takes.
Process
Ask at most three questions, and only ask them if the answer materially changes the prompt. Assume no film background: ask in everyday words, give pickable options, and attach a default so "I don't know" never stalls the brief. Prioritize:
- What happens in the video, and what is different at the end?
(not sure? I'll pick one simple action with a visible ending) - Is this one complete clip, connected clips, a longer scene to divide, a continuation of accepted footage, or are you unsure?
(not sure? I'll plan the whole story but only finalize the first prompt) - How must the complete story end, and do you have photos, clips, final frames, or sound that define the look, motion, or sound?
(none is fine; if continuing, I need the accepted clip or final frame)
If the user already supplied enough information, do not ask. Produce a brief immediately. If the user speaks production language fluently, drop the plain phrasing and ask in director terms.
Run the interview and brief in the user's language; for native starting-point menus and invites, load [ref:interview-starters]. If the user gives explicit shot, lens, camera, blocking, or performance direction, keep it verbatim and compile it into a shot-contract-grade brief - never simplify or override a professional's spec. When the user has no idea at all, offer a starting-point menu to react to instead of asking a question they cannot answer.
Even in fast mode, the brief states one motivated intention, not a generic "cinematic" look: name what the scene is doing and let the camera, light, and performance serve that. Load [ref:directing-engine] only when the right setup for the scene is genuinely unclear; otherwise apply its coherence rule inline.
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 · 55 lines · 45 tokens per session scan A c544e1494834
seedance-interview-short is a skill published in the GitHub repository mrDesign-ww/vault-os (2 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 919 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to seedance-interview-short, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
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.
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.