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 ZachArticulateV/designer-pro-and-seo --skill copywritinggit clone --depth 1 https://github.com/ZachArticulateV/designer-pro-and-seoWrote 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/zacharticulatev/designer-pro-and-seo/copywriting)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/copywriting"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/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/zacharticulatev/designer-pro-and-seo/copywriting"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/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.00089 | $0.00669 |
| Opus 5 | $0.00044 | $0.00334 |
| Sonnet 5 | $0.00018 | $0.00134 |
| Haiku 4.5 | $0.00009 | $0.00067 |
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 12d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
copywriting
Family: content-and-data Status: Stable
Purpose
Produce conversion copy that earns the click — the words a page needs, not a
critique of them. Fills the hole between design-cro (which reviews copy) and the
build (which needs copy to exist). Anchors every line to one audience and one
offer so it sounds specific, not generic.
Triggers
- "write copy" / "hero copy" / "rewrite this section"
- "headline" / "subhead"
- "value proposition" / "CTA copy"
- "make this convert"
Inputs
- Audience (who, and the problem they have) and the offer/product
- Page/section type (hero, features, pricing, CTA band, about)
- Desired tone (or pull from a design system / brand voice)
- Primary conversion action
Steps
- Anchor. State the one audience, their core pain, and the single desired action. All copy serves these three.
- Lead with outcome, not feature. Draft the headline as the result the user gets; the subhead earns belief; the body proves it.
- Write the set for the section type:
- Hero: headline + subhead + primary CTA (+ optional risk-reducer microcopy).
- Features: benefit-led blocks (benefit → how → proof), not feature lists.
- CTA band: a verb-first button label + one friction-reducing line.
- Apply the rules: one primary CTA, benefit before feature, concrete over vague, no jargon, headline readable in ~3 seconds, match search/ad intent.
- Offer 2–3 headline variants at different angles (outcome / objection / curiosity) so the user can A/B later.
- Pass to
design-croto pressure-test the result, or hand into a build brief (blast-promptBlueprint section).
Outputs
- Section-ready copy (headline, subhead, body, CTA, microcopy)
- 2–3 headline variants tagged by angle
- Notes on any claim that needs proof/substantiation before publishing
Dependencies
- None required (pure method).
Notes
Related skills: design-cro (pressure-tests the copy), blast-prompt (carries the
copy into a build brief), design-system-gen (tone) — composed, not hard-depended
(one-directional graph; keeps the copywriting↔design-cro edge out of Dependencies).
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.
- 12d ago First seen · 67 lines · 89 tokens per session scan A 823a705d4d90
copywriting is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 89 tokens to every session and 669 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
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…
figma-variable-audit
Audit Figma variable collections against token architecture best practices. Trigger when someone says: audit my Figma variables, check my Figma tokens, are my variables structured correctly, Figma variable health, review my variable collections, variable naming check, or anything about auditing the quality or…
governance-encoder
Convert governance policies into machine-executable JSON constraint files that AI agents and CI pipelines validate against automatically. This produces rule engine files in .ai/governance/, NOT narrative decision records or documentation. Trigger when someone says: encode governance rules, governance as code, automate…
system-benchmark
Benchmark a design system against industry standards and comparable public systems, producing a qualitative comparison across dimensions with specific, named reference points. Goes beyond an internal health assessment to answer 'how does our system compare to what good looks like out there?' Trigger when someone says…