email-sequences

email-sequences is a skill for Claude Code from brainbytes-dev/everything-claude-marketing. It costs 29 tokens per session (2,829 once invoked), scanned A, original, MIT.

A framework for planning automated email journeys, where different messages are sent after events such as sign-up, purchase, or inactivity.

In plain words
What is it for?
It helps design welcome, sales, onboarding, nurture, post-purchase, re-engagement, and win-back sequences.
Why use it?
It prevents email campaigns from becoming unfocused, mistimed, or conflicting with one another.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the everything-claude-marketing plugin — 72 skills, 22 commands, 18 agents, 2 hooks shipped together

Good fit It helps design welcome, sales, onboarding, nurture, post-purchase, re-engagement, and win-back sequences.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/brainbytes-dev/everything-claude-marketing/email-sequences
Install

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.

Any agent
npx skills add brainbytes-dev/everything-claude-marketing --skill email-sequences
Clone the repo
git clone --depth 1 https://github.com/brainbytes-dev/everything-claude-marketing

Made for: Claude Code.

Or install everything-claude-marketing, the plugin that ships this one along with the rest of its 72 skills, 22 commands, 18 agents, 2 hooks.

Wrote 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.

agentmods badge for email-sequences

README.md
[![agentmods](https://agentmods.dev/badge/skills/brainbytes-dev/everything-claude-marketing/email-sequences/github.svg)](https://agentmods.dev/skills/brainbytes-dev/everything-claude-marketing/email-sequences)
Your own site
<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.

agentmods 80×15 button for email-sequences

Your own site · 80×15
<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>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,829 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2mo ago against content hash 724d9750b0b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

skills/email/email-sequences/SKILL.md · 310 lines

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:

  1. What is the sequence type? (Welcome, nurture, sales, onboarding, re-engagement, post-purchase, winback)
  2. What triggers entry into the sequence? (Form submission, purchase, tag, date, inactivity)
  3. Who is the audience? (New leads, trial users, customers, lapsed users)
  4. What is the desired end action? (Purchase, book a call, activate a feature, renew)
  5. What is the product/service price point? (Affects sequence length and aggressiveness)
  6. What email platform is being used? (Capabilities vary)
  7. Are there existing sequences that could conflict?

Core Rules

  1. Every sequence needs a single, clear objective. If you can't state the goal in one sentence, the sequence is unfocused.
  2. Front-load value. The first 2-3 emails should deliver value with no ask. Earn the right to sell.
  3. Respect the relationship stage. A welcome sequence is an introduction, not a pitch meeting.
  4. Exit conditions are as important as entry conditions. Remove people who have already converted or who are in a conflicting sequence.
  5. Test spacing before testing copy. Wrong timing kills great copy.
  6. Every email must stand alone. Readers may skip emails — each one should make sense independently.
  7. 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

Read the full file on GitHub · 310 lines

Changes

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.

  1. 2mo ago First seen · 310 lines · 29 tokens per session scan A 724d9750b0b8

Subscribe to this mod's changes

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.

Related

email-sequences compared with skills from other repositories

email-sequences next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
email-sequencesbrainbytes-dev/everything-claude-marketingSkill107mo agoMITA29Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code