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 mfwarren/entrepreneur-claude-skills --skill email-campaignsgit clone --depth 1 https://github.com/mfwarren/entrepreneur-claude-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/mfwarren/entrepreneur-claude-skills/email-campaigns)<a href="https://agentmods.dev/skills/mfwarren/entrepreneur-claude-skills/email-campaigns"><img src="https://agentmods.dev/badge/skills/mfwarren/entrepreneur-claude-skills/email-campaigns/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/mfwarren/entrepreneur-claude-skills/email-campaigns"><img src="https://agentmods.dev/badge/skills/mfwarren/entrepreneur-claude-skills/email-campaigns.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.00004 | $0.00581 |
| Opus 5 | $0.00002 | $0.00291 |
| Sonnet 5 | $0.00001 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
email-campaigns 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.
What it actually says
Email Campaigns
Welcome sequences, launch campaigns, re-engagement flows, and segmentation strategy.
Purpose
Email is the highest-ROI marketing channel for most businesses. This skill creates structured email sequences with clear goals, not one-off blasts.
Workflow
Step 1: Gather Context
- Campaign type: welcome, launch, nurture, re-engagement, abandoned cart, winback
- Product/offer being promoted
- Audience segment
- Current list size and engagement
- Email platform (for formatting constraints)
Step 2: Sequence Design
- Define the campaign goal (sale, engagement, activation)
- Map the sequence: number of emails, timing, triggers
- For each email: subject line, preview text, body, CTA
- Segment logic: who gets what and when
Step 3: Write Emails
Each email follows:
- Subject line: Under 50 chars, curiosity or benefit-driven
- Preview text: Complements (doesn't repeat) the subject
- Opening line: Personal, relevant, no throat-clearing
- Body: One idea per email, conversational tone
- CTA: Single, clear action
- P.S.: Optional — use for urgency or secondary offer
Step 4: Segmentation Recommendations
- New vs. returning customers
- Engaged vs. cold subscribers
- Purchase history segments
- Behavioral triggers (opened, clicked, visited)
Output Format
## Email Campaign: [Type] — [Product/Offer]
### Sequence Overview
| # | Email | Send Day | Goal |
|---|-------|----------|------|
| 1 | [Name] | Day 0 | [Goal] |
| 2 | [Name] | Day 2 | [Goal] |
### Email 1: [Name]
**Subject:** [subject]
**Preview:** [preview text]
**Body:**
[email content]
**CTA:** [action]
Constraints
- One CTA per email — never compete with yourself
- Subject lines under 50 characters
- Emails under 200 words (exception: launch/story emails)
- Never use deceptive subject lines (fake RE:, misleading urgency)
- Include unsubscribe reference as a best practice note
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 · 85 lines · 4 tokens per session scan A 0664b7acc3ed
email-campaigns is a skill published in the GitHub repository mfwarren/entrepreneur-claude-skills (67 stars, last pushed 7mo ago), licensed MIT. It adds 4 tokens to every session and 581 once invoked, about $0.0000 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-30.
Other skills, from other repositories
modelchk
Size a task's run before spending it: the cheapest sufficient capability tier (fast, standard, frontier) and the reasoning effort within it, on a neutral scale that binds to whatever levels the model exposes. Use when work seems over- or under-powered, costly, ambiguous, or high-risk, or asks which model class and how…
re0-loop
Run repeated build -> QA -> re0-memo -> re0-work cycles while preserving learning and letting code die. Use for long agentic projects where progress must be measured by quality-cleared templates, reusable modules, and eliminated anti-patterns rather than hours spent or features accumulated.
autobahn
Carve guardrail-adjacent items out of scope with safe alternatives before risk-adjacent work starts, then run the safe remainder at full strength in a fresh subagent that only ever sees the carved prompt, never the risky input. Use when a task includes stealth, scraping, privacy, IP, policy, licensing, security, or…
re0-release
Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.
ssotize
Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Use when asked to find duplication, check consistency, locate the source of truth, deduplicate, consolidate, unify, or establish SSOT across artifacts or platforms. Starts…
re0-plan
Open a paperthin iteration's casebook before re0-loop's first turn — seeded with real content the moment the folder exists, never an empty directory. User-invoked, paperthin-only: assumes the full skill package installed. Run when opening a new build cycle in this repo.