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/procoders/superpowers-v/promo-clipnpx skills add procoders/superpowers-v --skill promo-clipgit clone --depth 1 https://github.com/procoders/superpowers-vWrote 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/procoders/superpowers-v/promo-clip)<a href="https://agentmods.dev/skills/procoders/superpowers-v/promo-clip"><img src="https://agentmods.dev/badge/skills/procoders/superpowers-v/promo-clip.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.1 | $0.00036 | $0.02940 |
| Opus 5 | $0.00018 | $0.01470 |
| Sonnet 5 | $0.00007 | $0.00588 |
| Haiku 4.5 | $0.00004 | $0.00294 |
Grade A, and why
promo-clip scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Extract, don't guess: `curl -s https://amiainative.dev` and its linked CSS, then How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Promo clips with Remotion
Overview
A promo clip is a script approved on paper, then a Remotion composition reviewed one still per scene before anything is rendered. Both failures we hit — three invisible scenes and a cut nobody could read — were caught by a still or by a human, never by the compiler.
Working reference, read it before writing scenes: /Users/oleg/Dev/cv-promo/src/Promo.tsx
(9 scenes, 1920×1080, 30 fps, TransitionSeries, inline styles, no CSS framework).
Script: script-v5-final.md · pain research + reference ad: pains-v1.md in the same repo.
Workflow
- Script table first, no code. One markdown table, columns
t · frames · on screen · motion/sound, plus a footer naming palette, fonts and spice level. Get an explicit approval on that table. Reason: rewriting a table is minutes, re-animating a scene is an hour. - Scaffold, then install — the scaffold does not install.
Pin the transitions package to the same version asnpx create-video@latest --yes --blank --no-tailwind ~/Dev/cv-promo cd ~/Dev/cv-promo && npm install npm i @remotion/[email protected] # EXACTLY the version of `remotion` in package.jsonremotion; a drifted pair breaks types.--no-tailwindbecause every style here is an inlinestyle={{}}object — cv-promo scaffolded with Tailwind and never used a single class. - One composition, one
<Sequence>(or<TransitionSeries.Sequence>) per scene. Scene durations live in one object;Root.tsximportsFPSandDURATIONfrom it. - Review stills before any render — one frame per scene, mid-scene, at half scale:
Read every PNG. A full render costs minutes; a still costs seconds and shows the same bug.npx remotion still Promo out/f200.png --frame=200 --scale=0.5 - Render only after the stills pass.
npx remotion render Promo out/promo.mp4
Three traps that cost us real time
1. <TransitionSeries> accepts only literal children
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 · 199 lines · 36 tokens per session scan A 0b241ef95d74
promo-clip is a skill published in the GitHub repository procoders/superpowers-v (36 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 2,940 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session.
write-documentation
Use when writing or substantially rewriting human-facing prose: documentation, README, guides, blog posts, emails, Slack messages, PR descriptions, release notes, or any text a human will read. Not for code comments, commit messages, or agent-to-agent communication.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
research-driven-development
Use when the user asks a question about a topic, requests research, or when understanding something is needed before planning. Triggers on "research this", "what is X", "how does Y work", "compare A vs B", "investigate", "deep dive", "look into".
document-release
Use when implementation on a branch is complete and it is about to be merged or PR'd — or when finishing-a-development-branch reaches its docs-audit gate — and after code changes are committed, to ensure all project documentation accurately reflects shipped code. Covers README, ARCHITECTURE, CONTRIBUTING, CHANGELOG…
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.