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 veo-generatorgit 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/veo-generator)<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/veo-generator"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/veo-generator/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/veo-generator"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/veo-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 16 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00095 | $0.01540 |
| Opus 5 | $0.00048 | $0.00770 |
| Sonnet 5 | $0.00019 | $0.00308 |
| Haiku 4.5 | $0.00010 | $0.00154 |
Grade A, and why
veo-generator 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 7d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Veo Generator
Turns an already-scripted shot package into actual video. The prompting is done
by the veo-showreel-production-kit skill (STYLE BIBLE → per-shot shots/*.md);
this skill is the render step that calls the Veo 3.1 API and downloads mp4s.
It expects the layout the production kit emits:
<Project>/
.env <- (optional) per-project API key lives here
video_production/
shots/shot_*.md <- source of truth: prompt, negative, seed, aspect, refs
storyboard/*.png <- first-frame sketches + 00_world_anchor.png
renders/ <- mp4 output (created here)
Each shots/shot_NN.md already contains everything the renderer needs: the
▶ Full Veo prompt block, the ⛔ Negative prompt block, and a
Reproduction & consistency line with the seed, aspect ratio, resolution,
reference image(s) and first-frame image. The renderer parses those — it never
re-invents the prompt.
Prerequisites
- The
pi-veoCLI (this package). Runs as TypeScript via pi's jiti loader — no build step. - ffmpeg — only needed for
--chain(seamless A→B last-frame handoff). Declared inpi.toolsand resolved via the tool registry; absent → non-chain videos still generate. - An API key (see below). Get one at https://aistudio.google.com/apikey.
Declared as an
envprobe (GEMINI_API_KEY) inpi.tools. The registry recognizesGEMINI_API_KEYonly — the CLI'sVEO_API_KEY/GOOGLE_API_KEYaliases still work at run time but are NOT tracked in Settings → Tools.
API key — per project or global
Resolution order, first non-empty wins:
| # | Source | Use |
|---|---|---|
| 1 | --api-key <KEY> flag |
one-off |
| 2 | VEO_API_KEY / GEMINI_API_KEY / GOOGLE_API_KEY env var |
machine-wide |
| 3 | <Project>/.env or …/video_production/.env |
per-project key |
| 4 | this package's .env |
global fallback |
Copy .env.example and set VEO_API_KEY=…. Never commit real keys.
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.
- 7d ago First seen · 119 lines · 95 tokens per session scan A 00dd4be72fda
veo-generator is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (278 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 1,540 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-09-03.
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-brainstorm
Pipeline orchestrator for brainstorming the cells architecture.
goga-define-challenge
Challenge the complete product definition before the PRD is generated.
goga-define-experience
Define the user experience required to achieve the established product goals and solve the identified problem.
goga-review-plan
Verify execution plan completeness and correctness.