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-interviewnpx skills add 1370998960-del/https-github.com-Emily2040-seedance-2.0 --skill seedance-interviewgit 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-interview)<a href="https://agentmods.dev/skills/1370998960-del/https-github.com-emily2040-seedance-2.0/seedance-interview"><img src="https://agentmods.dev/badge/skills/1370998960-del/https-github.com-emily2040-seedance-2.0/seedance-interview.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 | $0.00064 | $0.02336 |
| Opus 5 | $0.00032 | $0.01168 |
| Sonnet 5 | $0.00013 | $0.00467 |
| Haiku 4.5 | $0.00006 | $0.00234 |
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 5d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seedance-interview
Use this as the full director interview when the user has a rough idea rather than a ready scene. Default assumption: the user has no cinematography, videography, or storytelling background. They describe everyday life; this skill makes the film decisions. Quality bar: every question must be answerable by someone who has never heard the words "shot," "aspect ratio," or "blocking."
Intent
This is the front door, and the person walking through it is carrying something they care about and no vocabulary to ask for it. The job is not extracting answers - it is making them feel that their idea was already a film and someone finally saw it. Success sounds like "that's exactly what I meant." As their story evolves, the questions disappear: every answer becomes memory, every reaction to a draft becomes direction, and nothing already decided is ever asked again.
Question Quality Rules
- Ask in pictures, not parameters. Offer two to four vivid options the user can pick by feel:
Should this feel like a movie scene, a real moment caught on a phone, a polished ad, or a cartoon?Never:What camera style and aspect ratio? - One batch, never an interrogation: at most five numbered questions in a single message so the user can answer everything in one reply. Follow up only when an answer creates a real fork.
- Every question ships with a default. End it with
(not sure? I'll go with [default] - it works well). "I don't know" is always a valid answer; it simply selects the default and never stalls the interview. - One question, one decision. Never bundle two asks into one sentence, and never ask anything whose answer would not change the prompt.
- Keep their words. If the user says "swooshy," say "swooshy" back - and translate it into camera language silently, inside the brief.
- Expert detect: if the user speaks production language fluently (shot list, lens, deliverables, LUT, coverage) or works for an agency or production, drop plain mode, load
[ref:pro-filmmaking-standards], and run the professional intake instead.
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.
- 5d ago First seen · 106 lines · 64 tokens per session scan A 7a76b69a4d7e
seedance-interview 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 64 tokens to every session and 2,336 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-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 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.
unauth-api-flow-hijack
Exploit unauthenticated multi-step API flows without credentials.
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.