Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mikecann/agent-skillsnpx agentmods add skills/mikecann/agent-skills/motion-graphicsWrote 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/mikecann/agent-skills/motion-graphics)<a href="https://agentmods.dev/skills/mikecann/agent-skills/motion-graphics"><img src="https://agentmods.dev/badge/skills/mikecann/agent-skills/motion-graphics/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/mikecann/agent-skills/motion-graphics"><img src="https://agentmods.dev/badge/skills/mikecann/agent-skills/motion-graphics.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.00095 | $0.04419 |
| Opus 5.5 | $0.00038 | $0.01768 |
| Sonnet 5.5 | $0.00019 | $0.00884 |
| Haiku 4.5 | $0.00010 | $0.00442 |
Grade A, and why
motion-graphics 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 2mo 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Motion Graphics
Produce silent MP4 motion-graphic clips from a markdown video script using Remotion. The clips are overlay B-roll the user drops onto a 4K 30fps voiceover timeline in their video editor.
When to Use
Run this from a video folder — the folder holding source material for one YouTube video, e.g. C:\videos\rls\. Use when the user:
- says "build motion graphics for this video"
- pastes or points at a script and wants overlay clips made from it
- mid-edit, says "I want this part to be a motion graphic" — re-invoke and add one clip
Do not use this for full standalone explainer videos. The output is overlay content for an existing voice track.
Output Spec
Every clip the skill produces is:
- 3840 x 2160 (4K), 30 fps, H.264
- silent — no audio track. The user has their own voice recording.
- duration matches the natural read time of the script section it covers (see Phase 5). Most clips end up 2-15 seconds; longer is allowed but consider splitting (see "Long clips" below).
- rendered to
motion-graphics/out/<clip-id>-{A,B,C}.mp4
3 variants are rendered per clip. The user picks one. The other two MP4s move to out/_rejected/ (do not delete — keep for recovery). All three .tsx files stay in src/clips/.
Workflow
Phase 1 — Locate the script (pre-flight gate)
Before scaffolding or any other work, confirm a script exists in the video folder.
-
List
.mdfiles in the video folder (top level only, not in subfolders). -
If exactly one
.mdfile is found, silently use it as the script. Do not ask the user to confirm — they already pointed you at this folder. -
If multiple
.mdfiles are found, ask the user which one is the script (genuine ambiguity, can't guess). -
If none is found, stop immediately. Tell the user verbatim:
I couldn't find a
.mdscript in<folder>. Either drop the script there as a.mdfile, or paste the script content in chat now and I'll save it to<folder>/script.md.Then wait. If the user pastes the content, save it to
<folder>/script.mdfirst. Do not proceed past this phase until a script is on disk in the video folder. -
Once located, never modify the source file — it's the source of truth. The skill will work against a copy inside the Remotion project (see Phase 2).
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.
- 2mo ago First seen · 337 lines · 95 tokens per session scan A 420e11177e92
motion-graphics is a skill published in the GitHub repository mikecann/agent-skills (21 stars, last pushed 23d ago), licensed MIT. It adds 95 tokens to every session and 4,419 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…