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 Humblytics/humblytics-marketing-skills --skill email-sequencesgit clone --depth 1 https://github.com/Humblytics/humblytics-marketing-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/humblytics/humblytics-marketing-skills/email-sequences)<a href="https://agentmods.dev/skills/humblytics/humblytics-marketing-skills/email-sequences"><img src="https://agentmods.dev/badge/skills/humblytics/humblytics-marketing-skills/email-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.
<a href="https://agentmods.dev/skills/humblytics/humblytics-marketing-skills/email-sequences"><img src="https://agentmods.dev/badge/skills/humblytics/humblytics-marketing-skills/email-sequences.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00093 | $0.01659 |
| Opus 5 | $0.00046 | $0.00830 |
| Sonnet 5 | $0.00019 | $0.00332 |
| Haiku 4.5 | $0.00009 | $0.00166 |
Grade A, and why
email-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 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.
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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Sequences
Purpose
Design multi-email campaigns with complete copy, timing logic, subject lines, branching rules, and A/B test recommendations. Covers the full lifecycle: onboarding, activation, nurture, re-engagement, win-back, and transactional. Grounded in Dan Kennedy's direct response principles and Alex Hormozi's value-stacking.
When to Use
- Building an onboarding sequence for new signups or trial users
- Designing a lead nurture flow for top-of-funnel subscribers
- Writing a re-engagement or win-back campaign for churned users
- Creating an abandoned-cart or abandoned-trial recovery flow
- Planning a product launch email sequence
- Building a post-purchase upsell or cross-sell flow
Before You Start
Gather context before writing a single email:
- Product context — What does the product do? What's the value prop?
- Audience — Who's receiving this? What's their awareness stage?
- Goal — Activation? Trial-to-paid? Re-engagement? Referral?
- Entry trigger — What action enrolls them in this sequence?
- Exit triggers — What removes them? (purchase, unsubscribe, inactivity)
- Brand voice — Formal? Casual? Funny? Technical?
- Existing metrics — Open rate, CTR, and conversion benchmarks for calibration
Sequence Templates
1. Onboarding Sequence (5-7 emails)
Goal: Get user to activation milestone.
| # | Send | Subject | Purpose |
|---|---|---|---|
| 1 | Immediately | "Welcome to [Product] — your first win awaits" | Confirm signup, one action to take |
| 2 | +1 day | "The 60-second setup you skipped" | Re-prompt setup if incomplete |
| 3 | +3 days | "This is where most people get stuck" | Address common friction |
| 4 | +5 days | "A customer used [Product] to [result]" | Social proof + case study |
| 5 | +7 days | "What's next? Here's the roadmap" | Advanced features, community |
| 6 | +10 days | "Want a 1:1 walkthrough?" | Human touch for at-risk users |
| 7 | +14 days | "Your trial ends in 48 hours" | Conversion push (if trial) |
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.
- 12d ago First seen · 176 lines · 93 tokens per session scan A e9fb677ed826
email-sequences is a skill published in the GitHub repository Humblytics/humblytics-marketing-skills (83 stars, last pushed 7d ago), licensed MIT. It adds 93 tokens to every session and 1,659 once invoked, about $0.0005 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-30.
Other skills, from other repositories
ab-test-generator
Generate A/B test variants for affiliate content. Triggers on: "create A/B test", "test my headline", "optimize my CTA", "generate variants", "split test ideas", "improve click-through rate", "test my landing page copy", "headline alternatives", "CTA variations", "which version is better", "optimize conversions"…
authoring-ci-workflows
Use when adding or editing a GitHub Actions workflow, composite action, or reusable workflow under .github/ — new CI jobs, triggers, matrices, checkout/clone tuning, action pinning, GitHub App token auth, concurrency groups, timeout-minutes, paths filters, caching, or runner choice. Covers PostHog's workflow-authoring…
isolating-product-facade-contracts
Plan and execute product isolation migrations to a facade plus contract layer in PostHog, following the Visual review architecture. Use when a product still exposes internals (models/logic/views) across boundaries and needs migration toward contracts.py + facade/api.py + presentation separation, with a PR strategy…
debugging-mcp-analytics
Debug, support, and build PostHog MCP Analytics — product analytics for MCP servers (the @posthog/mcp and posthog.mcp SDKs plus the mcpanalytics product). Use when MCP analytics data looks wrong or missing ("events aren't showing", "intent clusters are empty", "sessions are missing", "per-tool numbers look wrong")…
qa-frontend
Internal PostHog developer frontend/browser QA skill. Use only when a PostHog developer explicitly asks to run frontend QA, browser-test a PR, verify a UI flow against the local PostHog stack, use qa-frontend, or QA current frontend changes with browser/runtime evidence. Do not use for generic code review, PR review…
triaging-merge-queue-failures
Decision procedure for a PR that failed or was removed from the Trunk merge queue: classify the kick (superseded by a newer commit, not mergeable, a gate that failed on a cancelled run, real failure, one-off flake, or repo-wide flaky/infra issue) and take the matching action (wait, hold and fix, requeue once, or…