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 The-AI-Directory-Company/agents-and-skills --skill email-campaign-writinggit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-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/the-ai-directory-company/agents-and-skills/email-campaign-writing)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/email-campaign-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/email-campaign-writing/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/the-ai-directory-company/agents-and-skills/email-campaign-writing"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/email-campaign-writing.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.00031 | $0.01602 |
| Opus 5 | $0.00015 | $0.00801 |
| Sonnet 5 | $0.00006 | $0.00320 |
| Haiku 4.5 | $0.00003 | $0.00160 |
Grade A, and why
email-campaign-writing 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 8d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Campaign Writing
Before you start
Gather the following from the user:
- Campaign type? (Welcome series, re-engagement, nurture, promotional, onboarding, abandoned cart)
- Who is the audience? (Segment definition — new signups, churned users, leads from specific channel)
- What action should the recipient take? (Activate account, book a demo, upgrade, read content)
- How many emails in the sequence? (Typical: welcome 3-5, nurture 5-8, re-engagement 3-4)
- What is the sending cadence? (Daily, every 2 days, weekly)
- What data do you have for personalization? (First name, company, plan type, last action)
If the user says "we need to send more emails," push back: "More emails without segmentation and a clear action per email just increases unsubscribes. What specific behavior should this sequence drive?"
Email sequence architecture
Define the full sequence before writing any individual email.
Sequence: [Name]
Goal: [Primary conversion action]
Audience: [Segment definition]
Emails: [Count]
Cadence: [Timing between emails]
Exit condition: [When to stop — e.g., user converts, unsubscribes]
| # | Send Timing | Purpose | Subject Line (A) | CTA |
|----|---------------|-------------------|---------------------------|------------------|
| 1 | Immediately | Welcome + orient | Welcome to [Product] | Complete setup |
| 2 | Day 2 | Quick win | Try [feature] in 2 min | Start tutorial |
| 3 | Day 5 | Social proof | How [Customer] uses [X] | Read case study |
| 4 | Day 8 | Value reminder | You're missing [benefit] | Activate feature |
| 5 | Day 14 | Nudge to convert | Your trial ends in 3 days | Upgrade now |
Single email template
Every email follows this structure. Keep total length under 200 words for transactional, under 400 for nurture.
FROM: [Sender name] <[email]>
SUBJECT: [Subject line — 6-10 words, under 50 chars]
PREVIEW TEXT: [First 90 chars visible in inbox — complements subject, never repeats it]
---
[Opening line — 1 sentence, references the recipient's situation or last action]
[Body — 2-3 short paragraphs. One idea per email. No walls of text.]
[CTA — single, clear button or link. One CTA per email, not three.]
[Sign-off — human name, not "The Team"]
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.
- 8d ago First seen · 146 lines · 31 tokens per session scan A 7f0452bd9524
email-campaign-writing is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 1,602 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-09-03.
Other skills, from other repositories
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
i18n-localization
Internationalization and localization for global applications. Use when adding multi-language support, handling regional formats, or preparing apps for global markets.
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.
finance
Financial analysis expertise for financial modeling (DCF, LBO, M&A), valuation, financial statement analysis, capital allocation, treasury management, and corporate finance decisions. Use when building financial models, analyzing statements, or making investment decisions.
investment-memo-generator
Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.