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/agentic-insights/foundry/copywriternpx skills add Agentic-Insights/foundry --skill copywritergit clone --depth 1 https://github.com/Agentic-Insights/foundryWrote 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/agentic-insights/foundry/copywriter)<a href="https://agentmods.dev/skills/agentic-insights/foundry/copywriter"><img src="https://agentmods.dev/badge/skills/agentic-insights/foundry/copywriter.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.00044 | $0.00578 |
| Opus 5 | $0.00022 | $0.00289 |
| Sonnet 5 | $0.00009 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
copywriter 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 3d 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.
What it actually says
Copywriter
Write clear, compelling copy for products, marketing, and UX.
Scope
| Type | Examples |
|---|---|
| UX Writing | Buttons, errors, empty states, tooltips, forms |
| Marketing | Landing pages, CTAs, feature descriptions |
| Product | Announcements, release notes, onboarding |
| Welcome, transactional, campaigns |
Core Formulas
Buttons
Verb + Noun → "Save Changes", "Start Free Trial" (not "Submit", "OK")
Errors
What happened → Why → How to fix
"Please enter a valid email address"
"Password must be at least 8 characters"
Empty States
Headline → Explanation → Action
"No results found" → "Try adjusting filters" → [Clear Filters]
CTAs
Verb + Benefit + Remove friction
"Start Free Trial" (not "Sign Up")
"Get Started Free" (not "Learn More")
Headlines
"How to [goal] without [pain point]"
"[Number] ways to [benefit]"
"Get [outcome] in [timeframe]"
Voice & Tone
Voice (consistent):
- Professional but friendly
- Clear and concise
- Helpful and supportive
Tone (varies):
| Context | Example |
|---|---|
| Success | "All set! Your changes are live." |
| Error | "Something went wrong, but your data is safe." |
| Urgency | "Action required: Suspicious login detected" |
Power Words
| Category | Words |
|---|---|
| Urgency | Now, Today, Limited, Fast |
| Value | Free, Save, Bonus, Extra |
| Trust | Guaranteed, Proven, Secure |
| Ease | Easy, Simple, Quick, Instant |
Checklist
- Clear? (12-year-old test)
- Concise? (Remove unnecessary words)
- Specific? (Numbers, examples)
- Actionable? (What should user do?)
- Scannable? (Headings, bullets)
References
- UX Patterns - Buttons, errors, forms, tooltips
- Marketing Copy - Landing pages, CTAs, emails
What ships with it
2 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.
- 3d ago First seen · 90 lines · 44 tokens per session scan A 22653c2136bd
copywriter is a skill published in the GitHub repository Agentic-Insights/foundry (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 578 once invoked, about $0.0002 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…