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/mblode/agent-skills/copywritingnpx skills add mblode/agent-skills --skill copywritinggit clone --depth 1 https://github.com/mblode/agent-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/mblode/agent-skills/copywriting)<a href="https://agentmods.dev/skills/mblode/agent-skills/copywriting"><img src="https://agentmods.dev/badge/skills/mblode/agent-skills/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.1 | $0.00068 | $0.04083 |
| Opus 5 | $0.00034 | $0.02041 |
| Sonnet 5 | $0.00014 | $0.00817 |
| Haiku 4.5 | $0.00007 | $0.00408 |
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 today.
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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copywriting
- IS: short conversion copy (landing pages, hero, subheads, CTAs, product descriptions, onboarding strings, email subjects); product-state strings (destructive CTAs, error, success, empty, loading, permission copy); stripping AI writing tells from any copy.
- IS NOT: long-form articles, posts, or anything written as a person rather than a brand (use the external
ghostwriterskill with platformblog), slide or deck copy (usepresentation-creator), API/product/reference docs (usedocs-writing), in-session assistant talk (useeli5), or deciding which action exists, its scope, consequence, reversibility, or reachable states (useproduct-design; this skill writes final wording once those are decided).
Two modes, auto-detected:
- Copy exists or the user pasted copy to fix: Mode B (Edit).
- Nothing written yet, or the user wants something new: Mode A (Write).
- Genuinely ambiguous ("improve this", no copy in scope): ask one question, then commit.
Reference files
| File | Read when |
|---|---|
references/frameworks.md |
Pick a framework by awareness stage (Write Step 4); audit against the frameworks (Edit Step 3) |
references/page-types.md |
Copy norms for a homepage, landing, pricing, feature, or about page (Write Step 4) |
references/word-lists.md |
Flag Tier 1/2/3 AI vocabulary (Edit Step 4) |
references/ai-patterns.md |
Flag structural, sentence-level, and drafting AI tells; P0/P1/P2 triage (Edit Step 4) |
references/sweeps.md |
Run the seven line-level sweeps, then the hyphenation pass (Edit Step 5) |
references/ui-states.md |
The copy is a product state or action label, not marketing (Write Step 4; Edit Step 6 before using [STATE-COPY]) |
references/voice-chart.md |
No usable voice file exists and the product needs one (Write Step 3; Edit Step 1); also holds the tone-by-reader-state table |
evals/evals.json |
Only when changing this skill: behavioural scenarios with assertions plus should-trigger and near-miss routing prompts. Never loads during a user task |
What ships with it
8 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.
- today Changed · -32 lines · -79 tokens per session 59152e614101
- 6d ago First seen · 297 lines · 147 tokens per session scan A 8f4d5ab1429b
copywriting is a skill published in the GitHub repository mblode/agent-skills (102 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 4,083 once invoked, about $0.0003 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
duckduckgo-search
Free keyless web, news, and image search via ddgs.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.