Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/dasein108/slope-studio/film-maker)<a href="https://agentmods.dev/skills/dasein108/slope-studio/film-maker"><img src="https://agentmods.dev/badge/skills/dasein108/slope-studio/film-maker/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/dasein108/slope-studio/film-maker"><img src="https://agentmods.dev/badge/skills/dasein108/slope-studio/film-maker.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.00096 | $0.07164 |
| Opus 5 | $0.00048 | $0.03582 |
| Sonnet 5 | $0.00019 | $0.01433 |
| Haiku 4.5 | $0.00010 | $0.00716 |
Grade A, and why
film-maker 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 12d 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 — 428 lines — stays where its author put it; the contents beside it link to each section on GitHub.
film-maker — Slope Studio operator guide
You are driving studio, a 7-stage CLI that turns a text idea into a finished
vertical Short. This skill tells you exactly how to run and observe each stage.
0. Environment check (do this first)
cd /Users/dasein/dev/slope-studio
source .venv/bin/activate 2>/dev/null || { uv venv && source .venv/bin/activate && uv pip install -e ".[fal]"; }
command -v ffmpeg ffprobe >/dev/null || echo "MISSING ffmpeg — install it"
studio --help # confirm the CLI is importable
Keys live in .env (gitignored). studio auto-detects them and picks providers;
FAL_KEY unlocks Nano Banana images + AI video. No keys → it still runs on the
free/offline path (stub script, stub images, kenburns video, edge voice).
1. The pipeline at a glance
script → visuals → narrate → clips → stitch → audio → voice → save → [publish]
① ② ②.5 ③ ④ ④.5 ⑤ ⑥ ⑦
Each stage reads/writes runs/<id>/. The manifest project.json records provider,
cost, latency, done-flag per stage. Stages are idempotent (skip if output exists;
--force to redo visuals/clips). audio ④.5 generates sfx + a music bed between
stitch and voice; the voice stage mixes them in (music ducked under narration). Sound
is a cheap, big quality lever — see guides §11.
narrate (stage ②.5, runs when voice is on) TTS-synthesizes each scene first,
so every clip lasts exactly as long as its narration → the final length follows the
speech (~target ±30s), perfectly synced, no truncation. It writes 05_voice/scenes/*.mp3,
05_voice/timing.json, and the aligned 05_voice/captions.srt.
Silent held beats — a scene with empty
narrationis NOT dropped:narrateemits silence for the scene's plannedduration_s(start→end) and holds the clip that long. Use this for wordless cinematic interludes (atmosphere skies, a held glow) that stretch a short text to a longer runtime — keep them moving (parallax/drift) and let themusicbed carry them so they read as breathing room, not dead air.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 428 lines · 96 tokens per session scan A ee82a1eea28f
film-maker is a skill published in the GitHub repository dasein108/slope-studio (3 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 7,164 once invoked, about $0.0005 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-31.
Other skills, from other repositories
dws
A command-line guide for DingTalk, a workplace platform with chat, documents, calendars, approvals, tasks, and other business tools.
package-author
A packaging guide for turning scripts, skills, or an MCP service into a standard plugin package. MCP is a way for an AI assistant to connect to external tools.
notes
Skill "notes" from Pinvou/pinvou-agent, covering ima notes, operations, write rules, examples and response handling.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.