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/find-iterationsnpx skills add Motion-Creative/motion-creative-plugin --skill find-iterationsgit 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.00092 | $0.02694 |
| Opus 5 | $0.00046 | $0.01347 |
| Sonnet 5 | $0.00018 | $0.00539 |
| Haiku 4.5 | $0.00009 | $0.00269 |
Grade A, and why
find-iterations 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Iteration Opportunities
Identify what's working, what's dying, and what specific iterations to test next. Every iteration card is specific enough to brief immediately.
Phase 0: Orient
- Acknowledge: "I'll identify what's fatiguing and suggest specific iterations to test."
- Ask if needed: "Any specific creatives you want to focus on, or should I scan everything and find the opportunities?"
- Connected workflow: After finding iterations, you can brief one (
/build-brief), write hooks for it (/write-hooks), or analyze the original ad (/analyze-ad).
If the user already specified what they want to iterate on, skip questions.
Phase 1: Setup
1a. Parse Arguments
--datePreset: Analysis window. Default:LAST_30_DAYS.--limit: Max creatives per metric. Default:10.
1b. Load Context
- Read
${CLAUDE_PLUGIN_ROOT}/motion-creative.config.mdfor primary KPI, brand guidelines, production constraints, competitors. If the file does not exist, use these defaults and suggest the user run/customize:primary_kpi: use goalMetric from firstget_creative_insightsresponsedefault_date_preset: LAST_30_DAYSdefault_creative_limit: 10priority_glossary_categories: use all- Brand guidelines + competitors: pull from Motion API
- Read
${CLAUDE_SKILL_DIR}/../creative-strategist/SKILL.mdfor methodology. - Read
${CLAUDE_SKILL_DIR}/../creative-strategist/references/performance-metrics.mdfor metric interpretation. - Read
${CLAUDE_SKILL_DIR}/../creative-strategist/references/concept-standards.mdfor quality bar. - Read
${CLAUDE_SKILL_DIR}/references/creative-diversity.mdfor diversity audit methodology, exploitation vs exploration framework, and "What to Build Next" prioritization. - Use
default_date_presetfrom settings as the datePreset for all calls unless the user provided a--datePresetargument. Usedefault_creative_limitfrom settings as the limit unless the user provided a--limitargument. - If settings specify
priority_glossary_categories, prioritize those categories in taxonomy analysis and gap detection.
What ships with it
1 file 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 First seen · 239 lines · 92 tokens per session scan A 87ffe19053de
find-iterations is a skill published in the GitHub repository Motion-Creative/motion-creative-plugin (20 stars, last pushed 3mo ago), licensed MIT. It adds 92 tokens to every session and 2,694 once invoked, about $0.0005 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
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…