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.
npx skills add varunk130/ai-gtm-skill-library --skill lead-nurturegit clone --depth 1 https://github.com/varunk130/ai-gtm-skill-libraryWrote 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.
[](https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/lead-nurture)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/lead-nurture"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/lead-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.
<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/lead-nurture"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/lead-nurture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00073 | $0.01317 |
| Opus 5 | $0.00036 | $0.00659 |
| Sonnet 5 | $0.00015 | $0.00263 |
| Haiku 4.5 | $0.00007 | $0.00132 |
Grade A, and why
lead-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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Nurture (NURTURE Framework)
Design a lead-nurture system that respects buyer intent, routes leads to the right next action, and stops sending eight more emails to people who already raised their hand. NURTURE replaces single-track drip sequences with multi-track journeys gated by behavioral signals.
Core Principle
Nurture fails when it treats time as the trigger. "Send email 3 on day 7" assumes every lead is on the same journey. NURTURE treats signal - not the calendar - as the trigger, and gates progression by demonstrated intent.
The NURTURE Framework
| Letter | Stage | The Question |
|---|---|---|
| N | Needs Mapping | What buying-stage needs does the lead currently have evidence of? |
| U | Understand Intent | What behavioral and explicit signals map to which stage? |
| R | Route to Track | Which nurture track does the lead enter, and on what entry criteria? |
| T | Trigger Progression | What signal moves the lead to the next step (or back)? |
| U | Upgrade to Sales | What threshold defines MQL → SQL handoff, and what's the SLA? |
| R | Recycle Cold | When does the lead exit the active track into long-cycle nurture? |
| E | Engagement Refresh | How is content kept current and personalization kept honest? |
Buying-Stage Nurture Tracks
| Stage | Lead State | Track Goal | Cadence |
|---|---|---|---|
| Unaware | Discovered category, no problem framing | Frame the problem | Bi-weekly |
| Aware | Acknowledges problem, exploring | Reframe with our POV | Weekly |
| Considering | Evaluating vendors | Differentiate + de-risk | 2-4×/week, behavior-gated |
| Decision | Short-listed | Accelerate to demo / sales | Daily during active window |
| Dormant / Lost | No activity 60+ days OR closed-lost | Reactivate on signal | Quarterly check-in + signal trigger |
Intent Signals
A robust nurture system reads explicit and behavioral signals together:
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.
- 10d ago First seen · 107 lines · 73 tokens per session scan A ee25295c5de5
lead-nurture is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (6 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 1,317 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.
Other skills, from other repositories
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…