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/build-briefnpx skills add Motion-Creative/motion-creative-plugin --skill build-briefgit clone --depth 1 https://github.com/Motion-Creative/motion-creative-pluginWrote 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/motion-creative/motion-creative-plugin/build-brief)<a href="https://agentmods.dev/skills/motion-creative/motion-creative-plugin/build-brief"><img src="https://agentmods.dev/badge/skills/motion-creative/motion-creative-plugin/build-brief.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.02244 |
| Opus 5 | $0.00017 | $0.01122 |
| Sonnet 5 | $0.00007 | $0.00449 |
| Haiku 4.5 | $0.00003 | $0.00224 |
Grade A, and why
build-brief 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Brief
Produce a production-ready creative brief from a concept — structured so a creative team can execute without follow-up questions. Uses the creative-strategist skill methodology and brief template standards.
Data accuracy: Every performance reference in the brief must cite a specific data point. If the brief references "top-performing hooks," cite which hooks and their metrics. Never include performance claims not grounded in tool data. If a data point is missing (e.g., no demographic data to inform targeting), flag it rather than guessing.
Phase 1: Get the Concept
1a. Parse Input
The $ARGUMENTS should contain one of:
- A concept description — freeform text describing what they want to make (e.g., "UGC problem-agitation ad targeting busy moms, hook about the 3pm energy crash")
- A reference to a concept from a previous
/create-conceptsrun — the user might say "brief concept 2" or paste a concept title - Empty — ask the user what to brief
If empty, use AskUserQuestion:
"What creative concept do you want to brief? You can describe the idea, paste a concept from
/create-concepts, or tell me the audience/angle you want to target and I'll build the concept."
1b. Get Auth Context
Call get_auth_context() for workspaceId.
Phase 2: Gather Strategic Inputs (Parallel)
The SPEND call must come first (it returns goalMetric and spendThreshold). Then dispatch remaining calls in parallel.
get_creative_insights(workspaceId, "SPEND", datePreset="LAST_30_DAYS", limit=5, withAggregatedInsights=true)— spend leaders + account-level aggregates
→ Extract goalMetric and spendThreshold from the response. If goalMetric.isCustomConversion is true, find the matching conversion in the customConversions array and include ["{id}_cost", "{id}_count"] in tableKPIs on all subsequent calls. Use goalMetric for all efficiency-sorted calls.
get_workspace_brand(workspaceId)— brand positioning, voice, visual identity, tone constraintsget_glossary_values(workspaceId)— creative taxonomy for alignmentget_creative_insights(workspaceId, insightType=goalMetric, datePreset="LAST_30_DAYS", limit=5)— efficiency leaders by workspace goal metric for visual reference
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 · 205 lines · 34 tokens per session scan A 5b334d84e9f7
build-brief is a skill published in the GitHub repository Motion-Creative/motion-creative-plugin (20 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 2,244 once invoked, about $0.0002 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…