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 agentmods add skills/dokkabei97/forged-claude-code/email-sequencenpx skills add Dokkabei97/forged-claude-code --skill email-sequencegit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/email-sequence)<a href="https://agentmods.dev/skills/dokkabei97/forged-claude-code/email-sequence"><img src="https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/email-sequence.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.01096 |
| Opus 5 | $0.00019 | $0.00548 |
| Sonnet 5 | $0.00008 | $0.00219 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
email-sequence 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 4d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Sequence - Drip Campaign Designer
Overview
Designs email sequences that convert signups into active users and active users into paying customers. Email is still the highest-ROI marketing channel.
1. When to Apply
| Trigger | Behavior |
|---|---|
| Setting up onboarding emails | Onboarding sequence template |
| "email sequence", "drip campaign" | Interactive sequence builder |
| Reducing churn | Win-back sequence template |
2. Sequence Types
Onboarding Sequence (5-7 emails, 14 days)
Day 0: Welcome + Quick Start (immediate after signup)
Day 1: Core Feature #1 (the "aha moment" trigger)
Day 3: Core Feature #2 (deepen engagement)
Day 5: Success Story (social proof)
Day 7: "Need Help?" (support + resources)
Day 10: Advanced Tip (power user features)
Day 14: Feedback Ask (NPS or survey)
Nurture Sequence (for leads not yet converted)
Week 1: Educational content (no pitch)
Week 2: Problem awareness (relate to their pain)
Week 3: Solution comparison (how category works)
Week 4: Your approach (soft product introduction)
Week 5: Case study (proof it works)
Week 6: Offer (free trial, demo, discount)
Win-Back Sequence (for inactive users)
Day 30 inactive: "We miss you" + what's new
Day 45 inactive: "Here's what you're missing" + value reminder
Day 60 inactive: "Last chance" + special offer
Day 90 inactive: "Should we close your account?" (triggers loss aversion)
Upsell Sequence (free → paid)
After N uses: Usage limit approaching
After activation: Feature comparison (free vs paid)
After value milestone: "You've achieved X, unlock more with Pro"
End of trial: Trial ending + conversion offer
3. Email Template
## Email [N]: [Internal Name]
**Send**: [Trigger / Timing]
**Subject**: [Subject Line A]
**Subject B**: [A/B Test Variant]
**Preheader**: [Preview text, 40-100 chars]
---
Hi {{first_name}},
[Opening — personal, relevant, short]
[Body — one key message, 3-5 short paragraphs max]
[CTA — single, clear call to action]
{{cta_button: "Button Text" → URL}}
[Closing — warm, brief]
[Signature]
[Name, Role]
[Company]
---
**Metrics to Track:**
- Open rate target: >30%
- Click rate target: >5%
- Unsubscribe threshold: <0.5%
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.
- 4d ago First seen · 169 lines · 38 tokens per session scan A 73b2a3a26fe5
email-sequence is a skill published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 1,096 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…