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 BlackBeltTechnology/pi-agent-dashboard --skill craft-video-postgit clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardWrote 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/blackbelttechnology/pi-agent-dashboard/craft-video-post)<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/craft-video-post"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/craft-video-post/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/blackbelttechnology/pi-agent-dashboard/craft-video-post"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/craft-video-post.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.00078 | $0.04804 |
| Opus 5.5 | $0.00031 | $0.01922 |
| Sonnet 5.5 | $0.00016 | $0.00961 |
| Haiku 4.5 | $0.00008 | $0.00480 |
Grade A, and why
craft-video-post 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 today.
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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
craft-video-post — footage → captions + overlays + mix → verified mp4
Chains FilmCraft (timeline, captions, export), EffectCraft (alpha graphics) and SoundCraft (mix) with the
sibling skills for redaction, transcription and code-driven motion. App dialects, traps and the
discover → execute → save → verify loop are in the app skills and in craft-studio; read filmcraft before
step 3. Resumable-job rules are in the craft-studio router, section Craft jobs.
Step table
| # | Step | Tool | Input → Output | Gate |
|---|---|---|---|---|
| 0 | Preflight + job | agent | request → job.json |
check: job |
| 1 | Footage | veo-generator / footage-redaction / user files |
clips → 01-footage/*.mp4 |
pi-craft verify per clip |
| 2 | Graphics (optional) | EffectCraft or hyperframes-showreel |
text/data → 02-graphics/*.mov (ProRes 4444 alpha) |
pi-craft verify --alpha |
| 3 | Assembly | FilmCraft | clips + overlays → 03-assembly/cut.mp4, ref.mp4 |
pi-craft verify --frame-diff |
| 4 | Captions input | video-transcription |
recording → 04-captions/cues.srt |
check: srt |
| 5 | Mix | SoundCraft | footage audio + music → 05-mix/mix.wav (PCM 24-bit 48 kHz) |
pi-craft verify --codec audio=pcm_s24le |
| 6 | Delivery | FilmCraft | project + mix + srt → 06-delivery/final.mp4 |
pi-craft verify h264 + aac |
Hand-off formats: wav PCM 24-bit 48 kHz (audio), mov ProRes 4444 with alpha (graphics), srt (captions), mp4 h264 + aac
(delivery). Duration tolerance: ±0.1 s for picture, ±0.05 s for audio. Write the tolerance as ${PIC}±0.1 — in bash
$PIC±0.1 swallows the ± into the variable name.
Step 0 — Preflight and job
Output: craft-jobs/<slug>/job.json (created or loaded).
Gate: check: job.
Check what is available before promising anything (soft references — no package is required):
| Sibling | Package | Check | If missing |
|---|---|---|---|
veo-generator |
video-production |
skill in the loaded skill list; pi-veo on PATH |
the user supplies footage files |
footage-redaction |
video-production |
skill in the loaded skill list | no redaction — say so and confirm the footage is safe to ship |
video-transcription |
video-transcription |
skill in the loaded skill list; command -v pi-transcribe |
offer to continue without captions (skip steps 4 and the caption part of 6), or ask for a ready .srt |
hyperframes-showreel |
video-production |
skill in the loaded skill list and npx hyperframes --version succeeds |
no code-driven overlays — use EffectCraft graphics only |
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.
- today First seen · 268 lines · 78 tokens per session scan A 6edff271c876
craft-video-post is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (321 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 4,804 once invoked, about $0.0003 per session on Opus 5.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-10-18.
Other skills, from other repositories
goga-cookbook
Principles for applying DSL specification in cell and CODEMANIFEST design.
goga-plan-by-design
Compile a design document into a ralphex execution plan.
goga-review-plan
Verify execution plan completeness and correctness.
goga-define-challenge
Challenge the complete product definition before the PRD is generated.
goga-define-project
Understand the current project before defining a product change that must fit into an existing product.
goga-define-requirements
Define the product requirements that describe what the product must do to deliver the established user experience and achieve the agreed product goals.