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 brainbytes-dev/everything-claude-marketing --skill email-sequencesgit clone --depth 1 https://github.com/brainbytes-dev/everything-claude-marketingWrote 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/brainbytes-dev/everything-claude-marketing/email-sequences)<a href="https://agentmods.dev/skills/brainbytes-dev/everything-claude-marketing/email-sequences"><img src="https://agentmods.dev/badge/skills/brainbytes-dev/everything-claude-marketing/email-sequences/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/brainbytes-dev/everything-claude-marketing/email-sequences"><img src="https://agentmods.dev/badge/skills/brainbytes-dev/everything-claude-marketing/email-sequences.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.00029 | $0.02829 |
| Opus 5.5 | $0.00012 | $0.01132 |
| Sonnet 5.5 | $0.00006 | $0.00566 |
| Haiku 4.5 | $0.00003 | $0.00283 |
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 2mo 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Sequences
When to Activate
Use this skill when:
- Building automated email sequences (welcome, nurture, sales, onboarding)
- Designing the architecture of email flows (triggers, delays, conditions)
- Planning email cadence and spacing
- Creating re-engagement or winback sequences
- Setting up post-purchase email flows
- Benchmarking sequence performance
First Questions
Before designing a sequence, clarify:
- What is the sequence type? (Welcome, nurture, sales, onboarding, re-engagement, post-purchase, winback)
- What triggers entry into the sequence? (Form submission, purchase, tag, date, inactivity)
- Who is the audience? (New leads, trial users, customers, lapsed users)
- What is the desired end action? (Purchase, book a call, activate a feature, renew)
- What is the product/service price point? (Affects sequence length and aggressiveness)
- What email platform is being used? (Capabilities vary)
- Are there existing sequences that could conflict?
Core Rules
- Every sequence needs a single, clear objective. If you can't state the goal in one sentence, the sequence is unfocused.
- Front-load value. The first 2-3 emails should deliver value with no ask. Earn the right to sell.
- Respect the relationship stage. A welcome sequence is an introduction, not a pitch meeting.
- Exit conditions are as important as entry conditions. Remove people who have already converted or who are in a conflicting sequence.
- Test spacing before testing copy. Wrong timing kills great copy.
- Every email must stand alone. Readers may skip emails — each one should make sense independently.
- Behavioral triggers outperform time-based triggers. "Visited pricing page" beats "Day 5 of sequence."
Sequence Architecture
The Building Blocks
TRIGGER (what starts the sequence)
|
v
DELAY (time between emails)
|
v
CONDITION (check before sending — is the person still qualified?)
|
v
EMAIL (the message)
|
v
BRANCH (if/then logic — what happened after the email?)
|
v
NEXT STEP or EXIT
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.
- 2mo ago First seen · 310 lines · 29 tokens per session scan A 724d9750b0b8
email-sequences is a skill published in the GitHub repository brainbytes-dev/everything-claude-marketing (10 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 2,829 once invoked, about $0.0001 per session on Opus 5.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.
email-sequences compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| email-sequencesbrainbytes-dev/everything-claude-marketing | Skill | 10 | 7mo ago | MIT | A | 29 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |