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/simota/agent-skills/directornpx skills add simota/agent-skills --skill directorgit clone --depth 1 https://github.com/simota/agent-skillsWrote 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/simota/agent-skills/director)<a href="https://agentmods.dev/skills/simota/agent-skills/director"><img src="https://agentmods.dev/badge/skills/simota/agent-skills/director.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.00037 | $0.06216 |
| Opus 5 | $0.00018 | $0.03108 |
| Sonnet 5 | $0.00007 | $0.01243 |
| Haiku 4.5 | $0.00004 | $0.00622 |
Grade A, and why
director 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Director
Demo video production specialist using Playwright E2E tests. Director designs scenarios, configures recording environments, and delivers reproducible feature demos that explain, not just display.
What ships with it
13 files 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.
- ARCHIVED_2026-08-19.md 748 B
- reference/autorun-schema.md 1.5 KB
- reference/captions-design.md 14 KB
- reference/checklist.md 7.8 KB
- reference/geo-packaging.md 8.4 KB
- reference/handoff-formats.md 9.6 KB
- reference/implementation-patterns.md 40 KB
- reference/playwright-config.md 36 KB
- reference/quality-metrics.md 6.8 KB
- reference/scenario-guidelines.md 24 KB
- reference/storytelling-archetypes.md 8.6 KB
- reference/thumbnail-design.md 12 KB
- reference/voiceover-design.md 13 KB
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 · 262 lines · 37 tokens per session scan A 625cdb8004dd
director is a skill published in the GitHub repository simota/agent-skills (75 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 6,216 once invoked, about $0.0002 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
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
stage-plan
How to turn "here is my material + here's the video I want" into a single, inspectable plan that spans reference images, reference videos, deterministic editing, semantic editing, generation, and composition. The output is project/plan.json — a cross-modal Edit Decision List (EDL) — which the assembler walks.…
frontend-design
Use this as the design-lead layer for VideoStudio COMPOSE work. It shapes project/composition/composition-manifest.json::artdirection and the model-authored HTML/SVG motion graphics in index.html.
stage-assemble
How to execute a validated, currently authorized project/plan.json into one finished file. Start/resume with production.status; if planapprovalcurrent is false, pass the state to gate-control and stop instead of producing or opening child gates. Walk the signed EDL; do not re-plan. Host-neutral: VideoStudio-specific…
image-compose
Read this skill after route lock for COMPOSE, or later in HYBRID, GENERATE, or EDIT only when deterministic copy, layout, diagram, framing, crop, mask, or overlay work is required. Do not preload it during routing. Keep the artifact in one stable directory containing image-manifest.json, index.html, and local assets.
image-router
Read this skill first and alone for every image creation or revision request. Return a locked route before reading any other ImageStudio skill; do not batch this read with craft, canvas, production, or review skills.