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/motion-creative/motion-creative-plugin/updatenpx skills add Motion-Creative/motion-creative-plugin --skill updategit clone --depth 1 https://github.com/Motion-Creative/motion-creative-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.00060 | $0.00560 |
| Opus 5 | $0.00030 | $0.00280 |
| Sonnet 5 | $0.00012 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
update 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 2d 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.
What it actually says
Update Motion Creative Plugin
Pull the latest version of the motion-creative plugin from GitHub and refresh the local cache.
Step 1: Locate Plugin Paths
Find the marketplace clone and cache directories:
MARKETPLACE_DIR="$HOME/.claude/plugins/marketplaces/motion-creative"
CACHE_BASE="$HOME/.claude/plugins/cache/motion-creative/motion-creative"
If $MARKETPLACE_DIR doesn't exist, tell the user the plugin isn't installed via marketplace and stop.
Step 2: Check Current State
# Current cached version
cat "$CACHE_BASE"/*/. claude-plugin/plugin.json 2>/dev/null | jq -r '.version'
# Current marketplace commit
git -C "$MARKETPLACE_DIR" rev-parse --short HEAD
Step 3: Pull Latest
git -C "$MARKETPLACE_DIR" pull origin main --ff-only
If the pull fails (e.g., network error, dirty state), report the error and stop. Do not force-reset.
Step 4: Refresh Cache
Copy the updated plugin files from the marketplace clone into the cache:
# Find the active cache version directory
INSTALL_DIR=$(ls -d "$CACHE_BASE"/*/ 2>/dev/null | head -1)
# Sync plugin contents (skills, config, MCP server)
rsync -a --delete "$MARKETPLACE_DIR/Plugin/" "$INSTALL_DIR/"
rsync --delete ensures removed files don't linger in the cache. The source is the Plugin/ directory from the repo — it contains .claude-plugin/, .mcp.json, skills/, and any other plugin files.
Step 5: Report
Show the user:
- Version: previous version -> new version (read from the updated
plugin.json) - Changes:
git -C "$MARKETPLACE_DIR" log --oneline <old-sha>..HEADto show what changed - Action needed: "Restart your Claude Code session or run
/reload-pluginsfor changes to take effect."
If already up to date (no new commits), say so: "You're on the latest version (vX.Y.Z)."
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.
- 2d ago First seen · 71 lines · 60 tokens per session scan A ad6e5be81ef0
update is a skill published in the GitHub repository Motion-Creative/motion-creative-plugin (20 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 560 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-30.
Other skills, from other repositories
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
agentmail
Use when an agent needs AgentMail CLI email inboxes.
skill-template
Template for creating new Agent Skills for context engineering. Use this template when adding new skills to the collection.
Agent Development
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development…
skill-creator
Scaffold a new yoyo skill when a human or community issue asks for one ("add a skill for X", "create a skill that does Y"). Generates correct frontmatter, validates, writes to disk.
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.