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 DojoCodingLabs/remotion-superpowers --skill add-transitionsgit clone --depth 1 https://github.com/DojoCodingLabs/remotion-superpowersWrote 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/dojocodinglabs/remotion-superpowers/add-transitions)<a href="https://agentmods.dev/skills/dojocodinglabs/remotion-superpowers/add-transitions"><img src="https://agentmods.dev/badge/skills/dojocodinglabs/remotion-superpowers/add-transitions/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/dojocodinglabs/remotion-superpowers/add-transitions"><img src="https://agentmods.dev/badge/skills/dojocodinglabs/remotion-superpowers/add-transitions.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.00039 | $0.01076 |
| Opus 5.5 | $0.00016 | $0.00430 |
| Sonnet 5.5 | $0.00008 | $0.00215 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
add-transitions 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Transitions — Scene Transition Wizard
You are helping the user add professional transitions between scenes in their Remotion composition. This skill is the Q&A and the creative call (which transition fits which cut). For the API, follow the official remotion-markup skill: transitions.md for TransitionSeries, presentations, timing, overlays and duration math, and light-leaks.md for light-leak overlays. Don't write transition code from memory.
Workflow
1. Check the Preview Is Running
Studio should already be open (npx remotion studio, or npx remotion studio --no-open with an in-app browser; open the URL it prints). If not, start it now so the user sees each transition as you add it.
2. Audit Current Scenes
Look at the current composition and identify the cut points:
grep -rlE "Sequence|TransitionSeries|Track" src/ --include="*.tsx" --include="*.ts"
List the scenes and ask where the user wants transitions. If the scenes are still a chain of <Sequence from> hard cuts, they move into <TransitionSeries> with one <TransitionSeries.Sequence> per scene, as official transitions.md shows (install @remotion/transitions with npx remotion add @remotion/transitions).
3. Choose Transition Types
Ask about the mood of each cut, then suggest:
| Transition | Effect | Best For |
|---|---|---|
fade |
Cross-dissolve between scenes | Universal, subtle; intros, outros, time passing |
slide |
Scene slides in from a direction | Energetic, modern; lists, step-by-step, social carousels |
wipe |
New scene wipes over old | Dramatic, reveals; before/after |
flip |
3D card flip | Playful, eye-catching; product variants, surprises |
clockWipe |
Clock-hand reveal | Creative, unique; countdowns, "later that day" |
| Light leak (overlay) | Warm flash of light over a hard cut | Cinematic energy without shortening the video; music drops, montages |
Slide directions: from-left, from-right, from-top, from-bottom. Slides should follow the visual flow (reading direction, or the direction something on screen is moving).
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 · 75 lines · 39 tokens per session scan A 3a7216cec616
add-transitions is a skill published in the GitHub repository DojoCodingLabs/remotion-superpowers (145 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 1,076 once invoked, about $0.0002 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-28.
Other skills, from other repositories
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…
prism-component
Implement a reusable, accessible, typed component from a design spec. Use when asked to "create a component", "build a widget", "implement this design", or "reusable UI element".
prism-ui
Implement a complete UI screen or feature from a Form visual spec. Use when asked to "build a page", "implement this screen", "build the frontend for this feature", or "create this UI".
spine-design
Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".
prism-dashboard
Build an internal dashboard with data tables, filters, detail views, and CRUD. Use when asked to build an "admin panel", "internal dashboard", "back office", or "data dashboard UI".
design-system-reference
Style guides and implementation rules for frontend design. Works with design-discovery agent which handles context gathering and VS-based style recommendations. Contains detailed style guides, anti-patterns, and implementation checklists.