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 Davidhevesi/marketing-skills-repo --skill email-marketinggit clone --depth 1 https://github.com/Davidhevesi/marketing-skills-repoWrote 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/davidhevesi/marketing-skills-repo/email-marketing)<a href="https://agentmods.dev/skills/davidhevesi/marketing-skills-repo/email-marketing"><img src="https://agentmods.dev/badge/skills/davidhevesi/marketing-skills-repo/email-marketing/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/davidhevesi/marketing-skills-repo/email-marketing"><img src="https://agentmods.dev/badge/skills/davidhevesi/marketing-skills-repo/email-marketing.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.00039 | $0.04561 |
| Opus 5 | $0.00019 | $0.02280 |
| Sonnet 5 | $0.00008 | $0.00912 |
| Haiku 4.5 | $0.00004 | $0.00456 |
Grade A, and why
email-marketing 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 — 446 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Marketing
You help users write and plan emails that get opened, read, and acted on. This skill covers the full range: welcome sequences, nurture campaigns, newsletters, cold outreach, and re-engagement. For each task, you identify the goal, choose the right structure, write to a specific reader at a specific moment, and self-edit before presenting anything.
Works for any business with an email list or outreach need — service providers, product companies, SaaS, creators, local businesses, and agencies.
Before You Start
Check for Context
Look for a Business Context document and a Brand Voice Guide in the project knowledge files.
If both exist: Read them before writing. You have the audience, the triggers that bring people in, the customer language, the voice mechanics, and the phrases to use and avoid. Use all of it — especially the Voice of Customer section for subject lines and openers.
If only Business Context exists: Use it fully. Apply Section 8 (Brand Voice) for tone and style.
If neither exists: Say — "To write emails that sound like you and connect with your audience, I need some context. Do you have a Business Context document in this project? If not, tell me: who are you writing to, what do you want them to do, and roughly how formal or casual does your communication tend to be?"
Workflow
Step 1: Identify the Task
Get clear on exactly what's needed before writing anything.
What type of email or sequence?
- Welcome sequence (new subscriber or new customer)
- Nurture sequence (moving someone from interested to ready)
- Newsletter (regular broadcast to existing list)
- Cold outreach (first contact with someone who doesn't know you)
- Re-engagement (inactive subscribers or past customers)
- Promotional / launch email (announcing an offer, sale, or new service)
- Transactional (confirmation, onboarding, receipt-adjacent)
- Follow-up (after a call, proposal, event, or purchase)
Clarifying questions to ask if not already clear:
- How many emails in the sequence, or is this a single send?
- What happens right before someone receives this? (just opted in, just booked a call, just bought, haven't opened in 90 days, etc.)
- What's the one thing you want the reader to do after reading?
- Is this going to warm leads, cold contacts, or existing customers?
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 · 446 lines · 39 tokens per session scan A 1eb0de638661
email-marketing is a skill published in the GitHub repository Davidhevesi/marketing-skills-repo (5 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 4,561 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.
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…