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 Vibe-Marketer/plugins-and-skills --skill copywritinggit clone --depth 1 https://github.com/Vibe-Marketer/plugins-and-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/vibe-marketer/plugins-and-skills/copywriting)<a href="https://agentmods.dev/skills/vibe-marketer/plugins-and-skills/copywriting"><img src="https://agentmods.dev/badge/skills/vibe-marketer/plugins-and-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/vibe-marketer/plugins-and-skills/copywriting"><img src="https://agentmods.dev/badge/skills/vibe-marketer/plugins-and-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.00071 | $0.01904 |
| Opus 5 | $0.00036 | $0.00952 |
| Sonnet 5 | $0.00014 | $0.00381 |
| Haiku 4.5 | $0.00007 | $0.00190 |
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 9d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<essential_principles> These rules apply to ALL copy this skill produces. No exceptions unless breaking a rule makes the writing clearer or more human.
<writing_rules>
- Concrete beats abstract. Show what you mean with real-world examples. "We helped 47 roofing companies double their leads" beats "We help businesses grow."
- Short beats long. Use "use" not "utilize." Use "help" not "facilitate." Use "now" not "at this point in time."
- Cut every unnecessary word. If removing a word doesn't change the meaning, remove it.
- Active beats passive. "We made this mistake" not "Mistakes were made." "This doubles your leads" not "Your leads can be doubled."
- Fresh beats cliched. Never write "game-changer," "revolutionary," "cutting-edge," "leverage," "synergy," "unlock your potential," or "take it to the next level." Say it in a way nobody has said it before.
- Simple beats clever. A confused reader never buys. If a 13-year-old can't understand it, rewrite it.
- Specific beats vague. Numbers, names, places, dates. "$47,000 in 90 days" beats "significant revenue fast."
- Honest beats euphemistic. Name problems directly. "Your ads are losing money" not "There may be optimization opportunities."
- One idea per sentence. If a sentence has two ideas, split it in two.
- Sound like a person. Read it aloud. If it sounds like a press release or a textbook, rewrite it until it sounds like you're talking to one person over coffee. </writing_rules>
<banned_words> Never use these unless quoting someone:
- utilize, leverage, synergy, optimize, facilitate, empower
- game-changer, revolutionary, cutting-edge, next-level, world-class
- unlock, unleash, supercharge, skyrocket, explode
- holistic, robust, seamless, scalable, paradigm
- thought leader, disrupt, innovate (as buzzwords)
- "in today's fast-paced world," "now more than ever"
- "at the end of the day," "it goes without saying"
Replace with plain words. "Use" not "utilize." "Improve" not "optimize." "Strong" not "robust." </banned_words>
<direct_response_dna> Every piece of copy must answer these questions:
- Who is this for? (Specific person, not "everyone")
- What do they want? (Desire, not feature)
- What's stopping them? (Real objection or belief)
- Why should they believe you? (Proof, not claims)
- What should they do next? (One clear action)
If the copy doesn't answer these, it's not done. </direct_response_dna> </essential_principles>
- Social media post - LinkedIn, X/Twitter, Facebook, Instagram
- Email - Cold email, newsletter, sequence, broadcast
- Ad copy - Facebook, Google, YouTube, print
- Headline - For any medium
- Sales page or landing page - Long or short form
- Review existing copy - Audit and improve what you have
Provide the topic, audience, and any source material. The more specific, the better.
If user provides content directly without selecting: Detect the type from context and route. If unclear, ask.
If user provides source material (transcripts, notes, ideas): Extract the core message, then route to the appropriate workflow.
<integration_with_other_skills> This skill works best when paired with these existing skills:
- buyer-persona - Know exactly who you're writing to
- belief-based-marketing - Understand what beliefs need to shift
- su-mechanism - Build the logical argument chain before writing
- offer-definition - Separate the Product (transformation) from Vehicle (delivery)
- competitive-analysis - Know what competitors say so you can say it differently
- icp-generator - Get specific targeting data for B2B copy
What ships with it
13 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.
- references/ai-copy-techniques.md 5.9 KB
- references/benson-edicts.md 18 KB
- references/copy-checklist.md 4.1 KB
- references/copy-frameworks.md 7.6 KB
- references/headline-formulas.md 5.7 KB
- references/platform-rules.md 5.4 KB
- references/writing-rules.md 11 KB
- workflows/review-copy.md 5.8 KB
- workflows/write-ad.md 3.8 KB
- workflows/write-email.md 4.0 KB
- workflows/write-headline.md 3.2 KB
- workflows/write-sales-page.md 7.1 KB
- workflows/write-social-post.md 5.1 KB
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.
- 9d ago First seen · 143 lines · 71 tokens per session scan A 4a71ec6082fc
copywriting is a skill published in the GitHub repository Vibe-Marketer/plugins-and-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 71 tokens to every session and 1,904 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…