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/rampstackco/claude-skills/email-sequencesnpx skills add rampstackco/claude-skills --skill email-sequencesgit clone --depth 1 https://github.com/rampstackco/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/rampstackco/claude-skills/email-sequences)<a href="https://agentmods.dev/skills/rampstackco/claude-skills/email-sequences"><img src="https://agentmods.dev/badge/skills/rampstackco/claude-skills/email-sequences.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.00121 | $0.02369 |
| Opus 5 | $0.00060 | $0.01184 |
| Sonnet 5 | $0.00024 | $0.00474 |
| Haiku 4.5 | $0.00012 | $0.00237 |
Grade A, and why
email-sequences 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 5d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Sequences
Plan and write email campaigns. Sequences (multi-message flows triggered by events) and broadcasts (one-off sends). Stack-agnostic. Works with any email service provider.
When to use
- Writing welcome and onboarding email sequences
- Planning lifecycle campaigns (activation, retention, win-back)
- Writing transactional emails (receipts, password resets, notifications)
- Newsletter design and writing
- Abandoned-cart or re-engagement flows
- Writing a one-off broadcast, launch announcement, or news email
- Drafting email subject lines and preview text for any send
When NOT to use
- Landing pages and conversion pages (use
landing-page-copy) - Long-form articles (use
content-and-copy) - Brand voice work (use
brand-voice) - Analytics setup for email (use
analytics-strategy)
Required inputs
- The audience (segment or list)
- The trigger or context (signup, purchase, abandonment, time-based, manual)
- The goal of the email or sequence
- Brand voice
- Any technical constraints (provider, deliverability requirements)
If the audience is undefined, define it before writing. Generic emails to "everyone" perform worse than targeted ones.
The framework: 6 sequence types
Most email programs run a handful of standard sequence patterns. Each has its own goals, structure, and pitfalls.
1. Welcome / onboarding
Triggered by signup. Goal: get the user to first value.
Typical structure (5 emails over 14 days):
- Email 1 (immediate): Welcome. Confirm they're in. State what happens next. Single CTA: the next obvious action.
- Email 2 (day 1 or 2): First-value step. Help them get to a quick win or core action.
- Email 3 (day 4 or 5): Education. Show them something they probably haven't discovered yet.
- Email 4 (day 8): Social proof. Customer story or use case relevant to their segment.
- Email 5 (day 14): Outcome reminder. Where they could be in 30/60/90 days. Soft commercial cue.
Common failure: Front-loading product features. Users don't care about features yet; they care about getting to value.
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.
- 5d ago First seen · 283 lines · 121 tokens per session scan A 1fae7c044e01
email-sequences is a skill published in the GitHub repository rampstackco/claude-skills (817 stars, last pushed 7d ago), licensed MIT. It adds 121 tokens to every session and 2,369 once invoked, about $0.0006 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
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
workflow
Professional AI programming assistant with structured workflow (Research -> Ideate -> Plan -> Execute -> Optimize -> Review) for developers.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
golden-rss
Use when testing the rss golden build.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.