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 samber/cc-skills --skill copywriting-hooksgit clone --depth 1 https://github.com/samber/cc-skillsWrote 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/samber/cc-skills/copywriting-hooks)<a href="https://agentmods.dev/skills/samber/cc-skills/copywriting-hooks"><img src="https://agentmods.dev/badge/skills/samber/cc-skills/copywriting-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/samber/cc-skills/copywriting-hooks"><img src="https://agentmods.dev/badge/skills/samber/cc-skills/copywriting-hooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00172 | $0.06705 |
| Opus 5 | $0.00086 | $0.03352 |
| Sonnet 5 | $0.00034 | $0.01341 |
| Haiku 4.5 | $0.00017 | $0.00671 |
Grade A, and why
copywriting-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 5d 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 — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copywriting Hooks
The method
A hook's only job is to make the reader want sentence 2. Voice, structure, formatting, all of it, follow from that one job.
What makes a reader want sentence 2 is one of five levers:
- Open a gap. Pose something incomplete that the reader needs to close. Curiosity gap, question, open loop.
- Break a prediction. State something that violates the reader's prior. Contrarian, definition reversal, surprising statistic.
- Drop into a scene. Load sensory or specific detail that builds a vivid frame. In medias res, concrete detail, time anchor.
- Promise a payoff. Name an outcome the reader wants. Benefit, "if you... then this", direct problem.
- Borrow weight. Lean on a name, number, or quote that carries embedded authority. Authority hook, statistic, quote with disagreement.
A strong hook usually pulls two levers at once. "Frank Sinatra, holding a glass of bourbon..." is scene plus open loop. "Most people think X. They're wrong." is prediction-break plus gap. Single-lever hooks can still work but are easier to ignore.
Three further principles:
- Specific beats abstract every time. Replace "many companies" with "Stripe, Shopify, Vercel". Replace "recently" with a date. Replace "studies show" with the actual finding or cut the claim.
- The first sentence must force the second. Read each candidate cold. If you would not click sentence 2 after sentence 1, rewrite.
- Match technique to article type. Personal essay does not open like a tutorial. See the type-fit table below.
Behavior
When this skill triggers:
- Confirm the brief. Topic, audience, target language (EN, FR, or both), approximate length, where it will be published. If any of these is unclear and material, ask before generating.
- Pick 3 to 4 hooks from the catalog below that are genuinely different. Different levers, not three flavors of contrarian.
- Write 2 candidates per hook, specific to the user's article. The two candidates within one hook should explore different angles (different anecdote, different statistic, different scene), not be rewordings of each other.
- Present using the Output format below.
- Ask through the question tool. The choice is a small fixed set, which is what that tool is for.
- Wait for the user's pick. Do not pick for them.
- After they pick, name what the choice commits the rest of the article to. A contrarian hook commits paragraphs 2 to 3 to defending the non-consensus claim. A scene opener commits the next section to either resolving the scene or productively delaying it.
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.
- 5d ago Changed · +8 lines · -59 tokens per session 53d2d421e168
- 10d ago First seen · 477 lines · 231 tokens per session scan A feaf886c5e21
copywriting-hooks is a skill published in the GitHub repository samber/cc-skills (208 stars, last pushed 3d ago), licensed MIT. It adds 172 tokens to every session and 6,705 once invoked, about $0.0009 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
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-benchmark
Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with…
golang-continuous-integration
GitHub Actions CI/CD pipeline configuration for Golang projects — workflow files for test, lint, SAST, coverage and vulnerability-scan jobs, Dependabot and Renovate config files, GoReleaser release pipelines, Docker build/push, repository security settings, and AI-driven PR review. Use when setting up or improving Go…
golang-documentation
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices.…
golang-observability
Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for…
golang-security
Security best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory safety, PII in logs, STRIDE/DREAD threat modeling, plus gosec SAST, race detection, and fuzz testing. Apply when writing…