cold-email-nurture

cold-email-nurture is a skill for Claude Code from cmj-hub/claude-cold-email. It costs 84 tokens per session (1,079 once invoked), scanned A, original, MIT.

A planner for a five-email nurture sequence, meaning follow-up messages for people who showed some interest but did not take the next step. It creates the subject, preview text, message structure, call to action, timing reason, and sales trigger for each email.

In plain words
What is it for?
Use it to design re-engagement campaigns, follow-ups after downloads or events, and sequences for inactive prospects or former customers.
Why use it?
It gives a consistent way to follow up with people who did not reply, became inactive, downloaded content, or attended an event. This avoids writing disconnected follow-up messages from scratch.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the cold-email plugin — 12 skills, 2 agents shipped together

Good fit Use it to design re-engagement campaigns, follow-ups after downloads or events, and sequences for inactive prospects or former customers.

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

Made for: Claude Code.

Or install cold-email, the plugin that ships this one along with the rest of its 12 skills, 2 agents.

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 cold-email-nurture

README.md
[![agentmods](https://agentmods.dev/badge/skills/cmj-hub/claude-cold-email/cold-email-nurture/github.svg)](https://agentmods.dev/skills/cmj-hub/claude-cold-email/cold-email-nurture)
Your own site
<a href="https://agentmods.dev/skills/cmj-hub/claude-cold-email/cold-email-nurture"><img src="https://agentmods.dev/badge/skills/cmj-hub/claude-cold-email/cold-email-nurture/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 cold-email-nurture

Your own site · 80×15
<a href="https://agentmods.dev/skills/cmj-hub/claude-cold-email/cold-email-nurture"><img src="https://agentmods.dev/badge/skills/cmj-hub/claude-cold-email/cold-email-nurture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,079 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.00084 $0.01079
Opus 5 $0.00042 $0.00540
Sonnet 5 $0.00017 $0.00216
Haiku 4.5 $0.00008 $0.00108

Measured 2d ago against content hash 623e0d8719e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

cold-email-nurture 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 2d 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/cold-email-nurture/SKILL.md · 125 lines

How it starts

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

Cold Email Nurture — 5-Email Stream Designer

Loaded by cold-email when the user wants to nurture (warm leads who didn't reply, re-engage dormant prospects, re-activate churned clients, post-content-download follow-ups).

Activation triggers

  • "Design a nurture sequence"
  • "5-email nurture"
  • "Re-engagement sequence"
  • "Re-activate churned"
  • "Post-download follow-up"
  • "Lifecycle nurture"

Workflow

1. Capture inputs

Required:

Input Source
pain_signal_profile The PSP for this audience
evp One-line value prop
nurture_context Why these prospects are getting this stream (no reply / churned / downloaded / post-event)
expected_cadence_days Default: 3 / 5 / 10 / 17 / 28

2. Generate the 5-email stream

Each email follows this shape:

Email N — <day> — <behavioral principle in 2 words>

Subject: <≤7 words>
Preheader: <≤90 chars>

Opener: <1 sentence — references the PSP, no "just checking in">
Body beats:
  - <Beat 1: insight / case / question>
  - <Beat 2: bridge to EVP>
CTA: <Binary, time-bound>
Cadence rationale: <Why this day>
Behavioral principle: <Reciprocity / commitment / social proof / loss aversion / curiosity>
Route-to-sales trigger: <Behavior that flags this lead is hot — open + reply + click + reply-to-CTA>

3. The default 5-email shape (no-reply nurture)

# Day Principle Job
1 3 Insight Drop ONE specific insight tied to the PSP. No ask.
2 8 Case study One peer company hit in . Binary ask.
3 13 Reframe Different angle on the same pain (cost-of-inaction / opportunity-cost).
4 23 Soft close "Should I keep these coming?" — explicit permission ask.
5 40 Hard close "I'll stop reaching out unless you want a different lens. Reply 'keep' to stay on."

For re-engagement / churned / post-download contexts, shift the opening principle but keep the 5-touch shape:

  • Re-engagement: T1 = "What changed?" (curiosity) → T5 = "Last ping — should I close the loop?"
  • Churned: T1 = "What broke?" (reciprocity by listening) → T5 = "If we shipped , would you re-evaluate?"
  • Post-download: T1 = "Most-asked Q after " (insight) → T5 = "Want a walkthrough or close the loop?"

Read the full file on GitHub · 125 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. 2d ago Changed · -1 lines 623e0d8719e9
  2. 11d ago First seen · 126 lines · 84 tokens per session scan A c8a6c6b2a1ff

Subscribe to this mod's changes

cold-email-nurture is a skill published in the GitHub repository cmj-hub/claude-cold-email (2 stars, last pushed 2d ago), licensed MIT. It adds 84 tokens to every session and 1,079 once invoked, about $0.0004 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-31.