Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Motion-Creative/motion-creative-plugin/plugin install motion-creativeWrote 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/write-hooks)<a href="https://agentmods.dev/skills/motion-creative/motion-creative-plugin/write-hooks"><img src="https://agentmods.dev/badge/skills/motion-creative/motion-creative-plugin/write-hooks/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/motion-creative/motion-creative-plugin/write-hooks"><img src="https://agentmods.dev/badge/skills/motion-creative/motion-creative-plugin/write-hooks.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.00085 | $0.02826 |
| Opus 5.5 | $0.00034 | $0.01130 |
| Sonnet 5.5 | $0.00017 | $0.00565 |
| Haiku 4.5 | $0.00009 | $0.00283 |
Grade A, and why
write-hooks 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 1mo 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hook Writing Engine
Generate psychologically-driven hooks that capture attention in the first 1-3 seconds of paid social ads. Every hook is grounded in workspace performance data from Motion.
Phase 0: Orient
- Acknowledge: "I'll generate hooks grounded in what's actually converting in your account."
- Ask if missing: "Product, target persona, and pain point? Or should I pull these from your workspace data?" If any required input is ambiguous, ask — don't assume.
- Important distinction: Hooks that stop the scroll and hooks that convert are often different. After generating, note which hooks optimize for attention vs. which optimize for action.
- Connected workflow: After hooks, you can brief the full ad (
/build-brief) or analyze how existing hooks perform (/analyze-ad).
If the user provided product, persona, and pain point clearly, skip questions.
Core Principle
A hook is the tactical expression of a messaging angle at a specific awareness stage. Before writing hooks, understand what the audience already knows and feels.
Hook Sources
Pain points are the most reliable hook source. Start here before trying other angles. See references/hook-sources.md for the full breakdown.
6 categories of pain-based hook material:
- Emotional pain points (start here) — what keeps them stuck, worried, or frustrated
- Daily annoyances — small friction the audience lives with every day
- Embarrassing habits — what they do but don't talk about
- Silent frustrations — what they tolerate because they think it's just normal
- Protective beliefs — what they tell themselves to avoid having to change
- Self-awareness moments — the truth they already half-know but haven't admitted
When generating a set of hooks, mine at least 2-3 different source categories to ensure emotional variety.
Phase 1: Gather Inputs
1a. Parse Arguments
Extract from $ARGUMENTS:
- Product: What does it do?
- Pain or Desire: What specific need does it address?
- Persona: Who are you targeting? (life context, not just demographics)
--stage: Awareness stage (unaware, problem-aware, solution-aware, product-aware, most-aware). Default: generate across all stages.--format: Video or static. Default: video.--count: How many hooks. Default: 10.
What ships with it
4 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.
- 1mo ago First seen · 251 lines · 85 tokens per session scan A f1901a2eb492
write-hooks is a skill published in the GitHub repository Motion-Creative/motion-creative-plugin (24 stars, last pushed 4mo ago), licensed MIT. It adds 85 tokens to every session and 2,826 once invoked, about $0.0003 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…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…