nurture-sequences

nurture-sequences is a skill for Claude Code from Arise-AI-Group/lead-management-plugin. It costs 0 tokens per session (2,195 once invoked), scanned A, original, Apache-2.0.

A system for keeping potential customers engaged with scheduled, useful emails matched to their sales stage. A lead is a person or company that may become a customer.

In plain words
What is it for?
Use it to draft personalized nurture emails, plan follow-ups for specific days, and decide when a lead should change stage. Connected tools can also support lead lookup, sending, and team notifications.
Why use it?
It helps prevent interested or unready leads from being forgotten while avoiding repeated sales pitches. It keeps track of when to continue, pause, advance, or stop communication.

Skill for Claude Code

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

Part of the lead-management plugin — 9 skills shipped together

Good fit Use it to draft personalized nurture emails, plan follow-ups for specific days, and decide when a lead should change stage. Connected tools can also support lead lookup, sending, and team notifications.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arise-ai-group/lead-management-plugin/nurture-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 Arise-AI-Group/lead-management-plugin --skill nurture-sequences
Clone the repo
git clone --depth 1 https://github.com/Arise-AI-Group/lead-management-plugin

Made for: Claude Code.

Or install lead-management, the plugin that ships this one along with the rest of its 9 skills.

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 nurture-sequences

README.md
[![agentmods](https://agentmods.dev/badge/skills/arise-ai-group/lead-management-plugin/nurture-sequences/github.svg)](https://agentmods.dev/skills/arise-ai-group/lead-management-plugin/nurture-sequences)
Your own site
<a href="https://agentmods.dev/skills/arise-ai-group/lead-management-plugin/nurture-sequences"><img src="https://agentmods.dev/badge/skills/arise-ai-group/lead-management-plugin/nurture-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 nurture-sequences

Your own site · 80×15
<a href="https://agentmods.dev/skills/arise-ai-group/lead-management-plugin/nurture-sequences"><img src="https://agentmods.dev/badge/skills/arise-ai-group/lead-management-plugin/nurture-sequences.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,195 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.00000 $0.02195
Opus 5 $0.00000 $0.01097
Sonnet 5 $0.00000 $0.00439
Haiku 4.5 $0.00000 $0.00219

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

Security

Grade A, and why

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

lead-management/skills/nurture-sequences/SKILL.md · 326 lines

How it starts

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

Nurture Sequences

Keep warm and cold leads engaged with stage-based email sequences that deliver value — not sales pitches — until they're ready to move forward.

How It Works

┌─────────────────────────────────────────────────────────────────┐
│                    NURTURE SEQUENCES                             │
├─────────────────────────────────────────────────────────────────┤
│  STANDALONE (always works)                                       │
│  ✓ You tell me: who to nurture, their context, their stage     │
│  ✓ Generate stage-appropriate email (value-first, not sales)    │
│  ✓ Content personalized to their industry and pain points       │
│  ✓ Track nurture cadence (Day 3 / 7 / 14 / 30 / 60+)          │
│  ✓ Recommend when to advance, pause, or exit a lead            │
├─────────────────────────────────────────────────────────────────┤
│  SUPERCHARGED (when you connect your tools)                      │
│  + CRM: Query all leads in nurture, auto-advance stages        │
│  + Email: Send nurture emails automatically                     │
│  + Chat: Notify team of replies, bounces, re-engagement signals│
└─────────────────────────────────────────────────────────────────┘

Getting Started

Required:

  • Contact name and company
  • Where they are in the nurture cadence (or "just entering nurture")

Helpful if you have it:

  • Their industry and company size
  • Pain points from discovery (if they've had a call)
  • What content they've received so far
  • Any recent activity (website visit, email open, social engagement)

If CRM is connected, I'll pull lead data and determine the nurture stage automatically.


Connectors (Optional)

Connector What It Adds
~~CRM Query leads by status, check activity, update nurture stage
~~email Send nurture emails automatically on schedule
~~chat Alert team when leads reply, bounce, or re-engage

No connectors? I'll draft the nurture email for you to send manually and track the cadence for you in conversation.

Read the full file on GitHub · 326 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 · 326 lines · 0 tokens per session scan A fdd0db179987

Subscribe to this mod's changes

nurture-sequences is a skill published in the GitHub repository Arise-AI-Group/lead-management-plugin (7 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,195 tokens. 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.

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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens