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 Engine-Room-Games/after-effects-mcp --skill after-effectsgit clone --depth 1 https://github.com/Engine-Room-Games/after-effects-mcpWrote 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/engine-room-games/after-effects-mcp/after-effects)<a href="https://agentmods.dev/skills/engine-room-games/after-effects-mcp/after-effects"><img src="https://agentmods.dev/badge/skills/engine-room-games/after-effects-mcp/after-effects/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/engine-room-games/after-effects-mcp/after-effects"><img src="https://agentmods.dev/badge/skills/engine-room-games/after-effects-mcp/after-effects.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.00070 | $0.08456 |
| Opus 5 | $0.00035 | $0.04228 |
| Sonnet 5 | $0.00014 | $0.01691 |
| Haiku 4.5 | $0.00007 | $0.00846 |
Grade A, and why
after-effects 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 3d 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 — 429 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Driving After Effects
You have direct control of a live After Effects session. The user sees every change immediately, and every tool call is a real undo step in their project. Work like a motion designer at the keyboard, not like a script that fires blind.
Two things sit behind this guide rather than in it, so they are not resident in
every session. Both are reachable either way — ae_guide({topic: …}) from any
client, or the file beside this one if you loaded this as a skill:
extendscript-gotchas(references/extendscript-gotchas.md) — read it before writing any raw ExtendScript forrun_jsx. Property lookups that return null, whatcopyToCompreally does, comp time versus layer time, the reserved words that stop a script before its first line.whats-new(references/whats-new.md) — what changed recently. Read it when a call behaves differently from what you expected, or the user says a tool used to work another way.
Read the house style first
get_house_style returns the style guide for the project that is currently open
— palette, type, motion defaults, layout rules — read from house-style.md
sitting next to the .aep file. Call it once at the start of any build task and
follow what it says. It costs one cheap call and it is the difference between
work that matches everything else the user has made and work that does not.
What comes back is a digest, not the document: the palette as named hexes,
the type, the motion defaults, the layout rules, and a note naming anything it
could not summarise. That is a few hundred tokens and it is what you build from.
Pass detail: "full" when you need the guide's own wording — and always before
set_house_style, which replaces the whole file, so you have to send the merged
document rather than a patch. A guide written as unstructured prose comes back
structured: false with its opening text, which is an honest "I could not read
this as a spec", not an empty answer.
If it reports found: false, build with sensible defaults and offer once, at the
end, to capture a style guide from what you just made. Don't nag about it.
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.
- 3d ago Changed · +189 lines 59754504779e
- 8d ago First seen · 240 lines · 70 tokens per session scan A 2a4125c8fe0d
after-effects is a skill published in the GitHub repository Engine-Room-Games/after-effects-mcp (7 stars, last pushed 3d ago), licensed MIT. It adds 70 tokens to every session and 8,456 once invoked, about $0.0003 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
edit-premiere-project
Inspect, edit, verify, save, and export an open Adobe Premiere Pro project through the premiere-pro MCP server. Use for rough cuts, timeline assembly or cleanup, clip and track changes, transitions and effects, dialogue or audio adjustments, captions, project organization, frame inspection, and delivery exports.
adobe-after-effects
Operational skill for Claude to automate After Effects via ExtendScript, expressions, render queue, compositions, and essential graphics pipelines.
talking-head-recut
Package an existing talking-head / interview / podcast video with timed, designed GRAPHIC OVERLAY cards — kinetic titles, lower-thirds, data callouts, quotes, side panels, picture-in-picture — synced to the transcript, on a 16:9 / 9:16 / 4:5 canvas of your choice; the clip plays untouched underneath. Trigger on…
embedded-captions
A workflow for adding captions or subtitles to an existing single-person talking-head video without changing the footage. Captions can appear as ordinary subtitles, behind the speaker, or as stylized visual effects.
faceless-explainer
Turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video: there is no site or footage to capture, so the visuals are invented per scene (typography, abstract graphics, diagrams, data-viz). Use for topic explainers, concept breakdowns, how-tos, listicles. Not a video built from a…
pr-to-video
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR…