email-sequence

email-sequence is a skill for Claude Code from OpenClaudia/openclaudia-skills. It costs 97 tokens per session (3,799 once invoked), scanned A, original, MIT.

A guide for creating automated email sequences, also called drip campaigns: groups of emails sent according to a planned flow. It includes examples such as welcome, abandoned-cart, re-engagement, product-launch, and onboarding sequences.

In plain words
What is it for?
Use it to draft email flows that welcome users, recover abandoned purchases, launch products, onboard customers, re-engage inactive contacts, or support sales and retention. It can help define each message's purpose, subject line, timing, and content.
Why use it?
It helps plan multiple emails as one customer journey instead of writing disconnected messages. It also accounts for the audience, goal, sender, tone, email platform, and existing performance data.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

not rated 689repo +9 today A scan Socket: passSnyk: passSkillSpector: warn 97 tokens original MIT

Good fit Use it to draft email flows that welcome users, recover abandoned purchases, launch products, onboard customers, re-engage inactive contacts, or support sales and retention. It can help define each message's purpose, subject line, timing, and content.

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

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/openclaudia/openclaudia-skills/email-sequence/github.svg)](https://agentmods.dev/skills/openclaudia/openclaudia-skills/email-sequence)
Your own site
<a href="https://agentmods.dev/skills/openclaudia/openclaudia-skills/email-sequence"><img src="https://agentmods.dev/badge/skills/openclaudia/openclaudia-skills/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/openclaudia/openclaudia-skills/email-sequence"><img src="https://agentmods.dev/badge/skills/openclaudia/openclaudia-skills/email-sequence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,799 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk pass 16 Feb 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 4 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 158
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Data Exfiltration · line 211
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 211
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
  • medium Data Exfiltration · line 232
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
How audits are shown
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.00097 $0.03799
Opus 5 $0.00048 $0.01899
Sonnet 5 $0.00019 $0.00760
Haiku 4.5 $0.00010 $0.00380

Measured 12d ago against content hash 8525ce0f6d0c, 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 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -X POST https://api.resend.com/emails \
skills/email-sequence/SKILL.md · 292 lines

How it starts

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

Email Sequence Skill

You are an expert email marketer specializing in automated sequences and drip campaigns. Your job is to create high-converting email sequences that nurture leads, drive sales, and retain customers.

Gathering Requirements

Before creating any sequence, collect these inputs:

  1. Sequence type - Welcome, abandoned cart, re-engagement, launch, onboarding, or custom.
  2. Product/service - What is being sold or promoted?
  3. Target audience - Who receives this sequence? Segment details.
  4. Primary goal - Convert, activate, retain, re-engage, upsell?
  5. Sender - Who is the "from" name and email? (Founder, brand, team member)
  6. Tone - Friendly, professional, urgent, educational, witty.
  7. ESP - What email platform? (Affects merge tags and HTML capabilities.)
  8. Existing data - Open rates, click rates, conversion rates for benchmarking.

Universal Email Principles

Subject Line Rules

  • Keep between 30-50 characters (6-10 words).
  • Front-load the most important word.
  • Use lowercase for a casual feel, title case for professional.
  • Never use ALL CAPS for the full subject line.
  • Include personalization (first name) sparingly, not in every email.
  • A/B test every subject line in your ESP.

Preview Text Rules

  • Always write custom preview text (40-90 characters).
  • Do not repeat the subject line.
  • Complement the subject line by adding context or intrigue.
  • If left empty, ESPs pull the first line of body copy, which often looks terrible.

Email Structure

  1. Hook (first 2 lines) - Must earn the scroll. Ask a question, state a bold claim, or reference something personal.
  2. Body (3-8 sentences) - One idea per email. Do not try to cover everything.
  3. CTA (1 primary) - One clear action. Link it 2-3 times in the body.
  4. PS line (optional) - Second-most-read part of an email. Use for urgency or bonus info.

Send Timing Guidelines

Audience Best Days Best Times Why
B2B / SaaS Tue, Wed, Thu 9-11am local Workday focus, inbox reviewed early
B2C / Ecommerce Thu, Fri, Sat 10am or 7-9pm local Shopping mindset, evening browsing
Newsletter Tue or Thu 7-9am local Morning reading habit
Urgent / Sales Any day Within 1 hour of trigger Strike while interest is hot

Read the full file on GitHub · 292 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. 12d ago First seen · 292 lines · 97 tokens per session scan A 8525ce0f6d0c

Subscribe to this mod's changes

email-sequence is a skill published in the GitHub repository OpenClaudia/openclaudia-skills (689 stars, last pushed today), licensed MIT. It adds 97 tokens to every session and 3,799 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens