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/remotion-dev/cursor-plugin/remotion-upgradenpx skills add remotion-dev/cursor-plugin --skill remotion-upgradegit clone --depth 1 https://github.com/remotion-dev/cursor-pluginWhat 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.00012 | $0.00427 |
| Opus 5 | $0.00006 | $0.00214 |
| Sonnet 5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
remotion-upgrade 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 yesterday.
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.
What it actually says
Upgrade Remotion
-
Inspect the project manifests and lockfile to identify the package manager and workspaces. Preserve unrelated changes.
-
Determine whether
@remotion/cliis locally available. If it is, run:npx remotion upgradeThis also updates project-local Remotion skills. Skip the manual upgrade below.
-
If
@remotion/cliis not available, upgrade manually:- Get the latest stable Remotion version with
npm view remotion version. - Find every installed
remotionand@remotion/*dependency across the project and upgrade them all to that exact version. Preserve their dependency sections and the project's workspace or catalog conventions. - Read the current Mediabunny compatibility page and determine the Mediabunny version compatible with the target Remotion version. Upgrade every installed
mediabunnyand@mediabunny/*package to the documented compatible version. - Run the project's package manager to update its lockfile.
- Get the latest stable Remotion version with
-
If
@remotion/cliis not available, update the installed Remotion skills:npx skills update remotion-best-practices remotion-captions remotion-create remotion-docs remotion-interactivity remotion-maps remotion-markup remotion-multimedia remotion-render remotion-saas remotion-studio remotion-upgrade --yes -
Review the manifest and lockfile diff. Ensure all Remotion packages use one version and all installed Mediabunny packages use the compatible version. If the CLI is available, run
npx remotion versionsas an additional check.
The Remotion releases contain the changelog and may be useful for summarizing relevant changes after the upgrade.
What ships with it
2 files 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.
- yesterday First seen · 32 lines · 12 tokens per session scan A 3c1b4e806e53
remotion-upgrade is a skill published in the GitHub repository remotion-dev/cursor-plugin (0 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 427 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.