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 no-session/claude-code-skills --skill copywritinggit clone --depth 1 https://github.com/no-session/claude-code-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/no-session/claude-code-skills/copywriting)<a href="https://agentmods.dev/skills/no-session/claude-code-skills/copywriting"><img src="https://agentmods.dev/badge/skills/no-session/claude-code-skills/copywriting/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/no-session/claude-code-skills/copywriting"><img src="https://agentmods.dev/badge/skills/no-session/claude-code-skills/copywriting.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.00133 | $0.06481 |
| Opus 5.5 | $0.00053 | $0.02592 |
| Sonnet 5.5 | $0.00027 | $0.01296 |
| Haiku 4.5 | $0.00013 | $0.00648 |
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 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 — 682 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copywriting
Agent Behavior
When triggered, follow this process:
1. Infer First, Ask Second
From the user's request, infer as much as possible: product, audience, tone, copy type, awareness level. Only ask about what you truly cannot infer. If you have enough to start, start — deliver a first draft and offer to refine.
Always infer:
- Copy type from context (if they say "landing page," don't ask "what type of copy?")
- Tone defaults to confident, clear, conversational unless specified
- Awareness level defaults to Solution-Aware for organic traffic, Problem-Aware for paid/cold traffic
Only ask when critical info is missing:
- What the product does (if not obvious from context)
- The specific desired action (trial, demo, signup)
- The unique mechanism (if you can't find or infer it)
2. Diagnose and Choose
- Match audience awareness level to framework (see Awareness Levels)
- Select copy length based on price point and decision complexity
- Pick positioning angle based on competitive context
3. Deliver
- Write the full copy in the appropriate format
- Include 3–5 headline variants
- Include 2–3 CTA variants
- Label each section clearly (Hero, Problem, Solution, Proof, CTA)
- Run the Pre-Delivery Checklist before presenting
4. Offer Next Steps
After delivering, offer: A/B variants, shorter/longer version, adaptation for a different channel.
First Principles
1. Copy Is Salesmanship in Writing
Its only purpose is to drive action — a sign-up, a demo booking, a trial start. Your landing page is the first salesperson a cold visitor meets. Treat it like a high-stakes conversation, not a brochure.
2. Write for "You," Not "We"
- Say "you" and "your" more than "we" and "our"
- Describe their problem, not your product history
- Use their words (from reviews, support tickets, calls) — not your jargon
3. Benefits Over Features
Push every feature through this chain:
Feature → "AI-powered analytics dashboard"
Advantage → "Insights update in real time, unlike manual reporting"
Benefit → "Save 15 hours/week on reporting"
Emotional Outcome → "Make decisions with confidence instead of second-guessing stale numbers"
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 · 682 lines · 133 tokens per session scan A 34d01a25bc94
copywriting is a skill published in the GitHub repository no-session/claude-code-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 133 tokens to every session and 6,481 once invoked, about $0.0005 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-31.
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…