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/tmj-90/gaffer/copywritingnpx skills add tmj-90/gaffer --skill copywritinggit clone --depth 1 https://github.com/tmj-90/gafferWrote 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/tmj-90/gaffer/copywriting)<a href="https://agentmods.dev/skills/tmj-90/gaffer/copywriting"><img src="https://agentmods.dev/badge/skills/tmj-90/gaffer/copywriting.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.00083 | $0.00979 |
| Opus 5 | $0.00042 | $0.00490 |
| Sonnet 5 | $0.00017 | $0.00196 |
| Haiku 4.5 | $0.00008 | $0.00098 |
Grade A, and why
copywriting 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write marketing copy that converts
Clarity beats cleverness every time. If you have to choose, choose clear.
Gather before writing (ask for missing pieces — one at a time)
- Page type — homepage, landing, pricing, feature, about?
- Primary action — the ONE thing visitors should do.
- Audience — who they are; what problem they're trying to solve; what language they use.
- Differentiation — what makes this meaningfully different from the obvious alternative?
- Proof points — numbers, testimonials, case studies, recognisable customers.
- Traffic source — organic, paid, email, direct? Awareness level changes the angle.
Core principles
Benefits, not features. Feature: "256-bit encryption". Benefit: "Your files are private — we can't read them, and neither can anyone else." Always translate mechanism → outcome → feeling.
Customer language. Use the words your users use to describe their problem. If interviews say "it's a nightmare to reconcile", the headline says "Stop the reconciliation nightmare" — not "Streamline financial operations."
Specificity > generality. "Save 2 hours a week" > "Save time". "4,200 teams" > "thousands of teams". Specific claims are more believable.
One idea per section. Each section of a page answers one question. Don't layer messages.
Headline formula bank
| Formula | Example | When to use |
|---|---|---|
| Outcome + timeframe | "Profitable in 90 days or your money back" | Strong guarantee; outcome is measurable |
| Problem reversal | "Stop losing deals to follow-up gaps" | Pain-aware audience |
| Social proof + outcome | "4,200 teams use Gaffer to ship twice as fast" | Strong install base |
| Who + outcome | "For developers who hate waiting on CI" | Niche audience; resonance over reach |
| Contrast | "The Stripe fees dashboard you always wanted" | Competitor-aware or category-aware audience |
CTA copy rules
- State what happens next: "Start free trial" (not "Get started"), "Book a 20-min demo" (not "Contact us").
- Match the commitment level to the page: cold traffic → low-commitment CTA (free trial, see pricing); warm traffic → higher-commitment CTA (book demo, talk to sales).
- Avoid: "Submit", "Click here", "Learn more" as primary CTAs.
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 First seen · 70 lines · 83 tokens per session scan A 969e794beb55
copywriting is a skill published in the GitHub repository tmj-90/gaffer (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 83 tokens to every session and 979 once invoked, about $0.0004 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-31.
Other skills, from other repositories
skill-creator
Create or update AnkaLoop skills. Use when designing, structuring, or packaging skills with scripts, references, and assets. This skill should be used when users want to create a new skill (or update an existing skill) that extends AnkaLoop's capabilities with specialized knowledge, workflows, or tool integrations.
ai-engineer
Expert knowledge in AI/ML development, model deployment, and MLOps practices.
gh-ci-analyzer
使用 gh CLI 分析 GitHub Actions CI 日志，提供结构化的故障诊断和报告.
security-best-practices
Security best practices and vulnerability prevention guidelines.
react-developer
Expert knowledge in React development, hooks, state management, and modern React patterns.
gh-pr-review
Review GitHub Pull Requests using the gh CLI. Use when a user asks to review a PR, perform code review, check a pull request, or provide feedback on proposed changes. Triggers on phrases like "review PR", "review pull request", "check PR", "code review".