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 matteotitta/genesys-skills --skill email-nurturegit clone --depth 1 https://github.com/matteotitta/genesys-skillsWrote 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/matteotitta/genesys-skills/email-nurture)<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/email-nurture"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/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.
<a href="https://agentmods.dev/skills/matteotitta/genesys-skills/email-nurture"><img src="https://agentmods.dev/badge/skills/matteotitta/genesys-skills/email-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.00023 | $0.01824 |
| Opus 5 | $0.00012 | $0.00912 |
| Sonnet 5 | $0.00005 | $0.00365 |
| Haiku 4.5 | $0.00002 | $0.00182 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Nurture
Create email nurture sequences that move prospects from content engagement to demo request, and from demo to closed deal. Focused on marketing automation sequences — not transactional or onboarding emails.
For full process, sequence templates, and email writing formulas → the premium reference.
Doctrine inherited (Step 7 — 0626 rollout)
Output complies with:
output-tenets.md— the seven tenetsoutput-simplicity.md— length caps, three-layer source placement, robot-tells banmarketing-psychology.md— 8 anchored heuristics (Rule of 7, loss aversion, JTBD)- Step 6 calibration: see [[feedback_execution_doctrine_refinements_step6]]
Refinements applied to this skill:
| Code | Refinement | How it lands in email-nurture |
|---|---|---|
| R1 | Source placement (three layers) | Emails are end-customer-facing. No sources block in body. Internal QA cites live in working draft only; stripped before scheduling. |
| R3 | Product-update tone | Any product/feature mention in nurture frames as "[Product] now does X" not "we're thrilled to announce." Even feature-launch nurture sequences. |
| R5 | Blog as voice anchor | For content-follow-up sequences with an anchor blog/whitepaper, the email opener mirrors the blog's opening line verbatim. Channel-voice drift is the biggest tell of multi-author sequences. |
| R6 | CTA hierarchy | Nurture targets prospects already in pipeline (warm-base). Product-action CTA primary (book a demo, start trial, open feature). Blog as fallback for not-ready-yet prospects. Never sign-up as primary (they're already signed up). |
| R9 | Action-oriented section names | "How to upgrade" beats "Upgrade options." "Why [Product]" beats "About us." Verb-led across every email's subject + sections. |
Claude Code Triggers
Invoke this skill when user says:
- "Email nurture sequence"
- "Post-download emails"
- "Demo follow-up emails"
- "Lead nurture sequence"
- "Content follow-up emails"
- "MQL nurture"
- "Email drip campaign"
- "Nurture sequence for [content]"
- "Follow-up sequence"
- "Re-engagement emails"
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.
- 9d ago First seen · 194 lines · 94 tokens per session scan A 7c930270d254
email-nurture is a skill published in the GitHub repository matteotitta/genesys-skills (36 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 1,824 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
gingiris-b2b-growth
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns.…
gr-b2b-growth
A guide to growing a business-to-business software product from early user research to large-scale sales. B2B software is sold to companies rather than individual consumers.
go-to-market-playbook
A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.
gingiris-go-global
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles.…
gr-competitor-research
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.