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 commands/dojocodinglabs/remotion-superpowers/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/commands/dojocodinglabs/remotion-superpowers/add-transitions)<a href="https://agentmods.dev/commands/dojocodinglabs/remotion-superpowers/add-transitions"><img src="https://agentmods.dev/badge/commands/dojocodinglabs/remotion-superpowers/add-transitions.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.00998 |
| Opus 5 | $0.00018 | $0.00499 |
| Sonnet 5 | $0.00007 | $0.00200 |
| Haiku 4.5 | $0.00004 | $0.00100 |
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 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 — 150 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 using @remotion/transitions.
Workflow
1. Install Transitions Package
npx remotion add @remotion/transitions
2. Audit Current Scenes
Look at the current composition and identify where transitions should go:
# Find scene components
grep -r "Sequence" src/ --include="*.tsx" --include="*.ts" -l
List the scenes and ask where the user wants transitions.
3. Choose Transition Types
Available transitions from @remotion/transitions:
| Transition | Effect | Best For |
|---|---|---|
fade |
Cross-dissolve between scenes | Universal, subtle |
slide |
Scene slides in from a direction | Energetic, modern |
wipe |
New scene wipes over old | Dramatic, reveals |
flip |
3D card flip | Playful, eye-catching |
clockWipe |
Clock-hand reveal | Creative, unique |
Slide directions: from-left, from-right, from-top, from-bottom
4. Choose Timing
| Timing | Feel | Code |
|---|---|---|
| Linear | Constant speed, mechanical | linearTiming({ durationInFrames: 20 }) |
| Spring | Organic, natural bounce | springTiming({ config: { damping: 200 }, durationInFrames: 25 }) |
Recommended: Spring timing for most transitions — feels more natural.
5. Refactor to TransitionSeries
Convert from <Sequence> to <TransitionSeries>:
Before (hard cuts):
<Sequence from={0} durationInFrames={90}>
<SceneA />
</Sequence>
<Sequence from={90} durationInFrames={90}>
<SceneB />
</Sequence>
<Sequence from={180} durationInFrames={90}>
<SceneC />
</Sequence>
After (smooth transitions):
import { TransitionSeries, linearTiming, springTiming } from "@remotion/transitions";
import { fade } from "@remotion/transitions/fade";
import { slide } from "@remotion/transitions/slide";
<TransitionSeries>
<TransitionSeries.Sequence durationInFrames={90}>
<SceneA />
</TransitionSeries.Sequence>
<TransitionSeries.Transition
presentation={fade()}
timing={springTiming({ config: { damping: 200 }, durationInFrames: 20 })}
/>
<TransitionSeries.Sequence durationInFrames={90}>
<SceneB />
</TransitionSeries.Sequence>
<TransitionSeries.Transition
presentation={slide({ direction: "from-right" })}
timing={linearTiming({ durationInFrames: 15 })}
/>
<TransitionSeries.Sequence durationInFrames={90}>
<SceneC />
</TransitionSeries.Sequence>
</TransitionSeries>
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 · 150 lines · 37 tokens per session scan A e3e660701baf
add-transitions is a command published in the GitHub repository DojoCodingLabs/remotion-superpowers (116 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 998 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 commands, from other repositories
generate-all
Generate creative assets for all posts in the current month's calendar.
cost-report
Show API cost breakdown for the current month's production.
brand-setup
Configure a new brand profile with colors, fonts, logo, visual style, platforms, and compliance rules.
edit-image
Edit a generated image — adjust background, lighting, colors, or composition.
index-assets
Index or re-index a brand's visual asset library.
status
Show current production status for the active brand and month.