email-sequence

email-sequence is a skill for Claude Code from nota-america/forgecat-agent-profiles. It costs 72 tokens per session (2,404 once invoked), scanned A, a copy of email-sequence, Apache-2.0.

A design for a series of timed marketing emails, including their text, branching rules, stopping conditions, and performance measures.

In plain words
What is it for?
Use it to create onboarding, lead-nurture, re-engagement, product-launch, win-back, and other drip email campaigns.
Why use it?
It organizes follow-up messages so recipients can receive different emails based on their actions or stage in a customer journey.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it to create onboarding, lead-nurture, re-engagement, product-launch, win-back, and other drip email campaigns.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nota-america/forgecat-agent-profiles/email-sequence
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 nota-america/forgecat-agent-profiles --skill email-sequence
Clone the repo
git clone --depth 1 https://github.com/nota-america/forgecat-agent-profiles

Made for: Claude Code.

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-sequence

README.md
[![agentmods](https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/email-sequence/github.svg)](https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/email-sequence)
Your own site
<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/email-sequence"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/email-sequence/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-sequence

Your own site · 80×15
<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/email-sequence"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/email-sequence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,404 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 95% copy Near-identical to another mod 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.00072 $0.02404
Opus 5 $0.00036 $0.01202
Sonnet 5 $0.00014 $0.00481
Haiku 4.5 $0.00007 $0.00240

Measured 9d ago against content hash 48306a297782, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

email-sequence 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 9d 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.

Origin

This is a copy

95% identical to email-sequence — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

profiles/anthropics/knowledge-work-plugins/anthropics_knowledge-work-plugins_marketing/for-claude/.claude/skills/email-sequence/SKILL.md · 225 lines

How it starts

The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Email Sequence

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (.forgecat/profiles/@forgecat/anthropics_knowledge-work-plugins_marketing/CONNECTORS.md).

Design and draft complete email sequences with full copy, timing, branching logic, and performance benchmarks for any lifecycle or campaign use case.

Trigger

User runs /email-sequence or asks to create, design, build, or draft an email sequence, drip campaign, nurture flow, or onboarding series.

Inputs

Gather the following from the user. If not provided, ask before proceeding:

  1. Sequence type — one of:

    • Onboarding
    • Lead nurture
    • Re-engagement
    • Product launch
    • Event follow-up
    • Upgrade/upsell
    • Win-back
    • Educational drip
  2. Goal — what the sequence should achieve (e.g., activate new users, convert leads to customers, reduce churn, drive event attendance, upsell to a higher tier)

  3. Audience — who receives this sequence, what stage they are at, and any relevant segmentation details (role, industry, behavior triggers, lifecycle stage)

  4. Number of emails (optional) — if not specified, recommend a count based on the sequence type using the templates in the Sequence Type Templates section below

  5. Timing/cadence preferences (optional) — desired spacing between emails (e.g., "every 3 days", "weekly", "aggressive first week then taper off")

  6. Brand voice — if configured in local settings, apply automatically and inform the user. If not configured, ask: "Do you have brand voice guidelines I should follow? If not, I'll use a clear, conversational professional tone."

  7. Additional context (optional):

    • Specific offers, discounts, or incentives to include
    • CTAs or landing pages to link to
    • Content assets available (blog posts, case studies, videos, guides)
    • Product features to highlight
    • Competitor differentiators to reference

Process

1. Sequence Strategy

Before drafting any emails, define the overall sequence architecture:

Read the full file on GitHub · 225 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. 9d ago First seen · 225 lines · 72 tokens per session scan A 48306a297782

Subscribe to this mod's changes

email-sequence is a skill published in the GitHub repository nota-america/forgecat-agent-profiles (66 stars, last pushed yesterday), licensed Apache-2.0. It adds 72 tokens to every session and 2,404 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to email-sequence, differing in 8 lines, and is treated as a copy.