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/rajitsaha/100xprism/email-sequencenpx skills add rajitsaha/100xprism --skill email-sequencegit clone --depth 1 https://github.com/rajitsaha/100xprismWrote 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/rajitsaha/100xprism/email-sequence)<a href="https://agentmods.dev/skills/rajitsaha/100xprism/email-sequence"><img src="https://agentmods.dev/badge/skills/rajitsaha/100xprism/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.1 | $0.00077 | $0.01865 |
| Opus 5 | $0.00039 | $0.00932 |
| Sonnet 5 | $0.00015 | $0.00373 |
| Haiku 4.5 | $0.00008 | $0.00186 |
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 6d 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.
This is a copy
86% identical to emails — 191 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Sequence Design
Initial Assessment
Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.
Establish:
- Sequence Type — welcome/onboarding, lead nurture, re-engagement, post-purchase, event-based, educational, or sales
- Audience Context — who they are, what triggered them into this sequence, what they already know/believe, current relationship with you
- Goals — primary conversion goal, relationship-building goals, segmentation goals, what defines success
Core Principles
1. One Email, One Job
One primary purpose and one main CTA per email — don't try to do everything.
2. Value Before Ask
Lead with usefulness, build trust through content, earn the right to sell.
3. Relevance Over Volume
Fewer, better emails win. Segment for relevance. Quality > frequency.
4. Clear Path Forward
Every email moves them somewhere. Links should do something useful. Make next steps obvious.
Email Sequence Strategy
Sequence Length
Welcome 3-7 emails; lead nurture 5-10; onboarding 5-10; re-engagement 3-5 — scaled by sales cycle length, product complexity, and relationship stage.
Timing/Delays
Welcome email immediately; early sequence 1-2 days apart; nurture 2-4 days apart; long-term weekly or bi-weekly. B2B: avoid weekends. B2C: test weekends. Send at local time.
Subject Line Strategy
Clear > clever. Specific > vague. Benefit or curiosity-driven. 40-60 characters ideal. Test emoji (they're polarizing).
Patterns that work:
- Question: "Still struggling with X?"
- How-to: "How to [achieve outcome] in [timeframe]"
- Number: "3 ways to [benefit]"
- Direct: "[First name], your [thing] is ready"
- Story tease: "The mistake I made with [topic]"
Preview Text
Extends the subject line, ~90-140 characters. Don't repeat the subject — complete the thought or add intrigue.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 207 lines · 77 tokens per session scan A 17569636780b
email-sequence is a skill published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 6d ago), licensed MIT. It adds 77 tokens to every session and 1,865 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to emails, differing in 191 lines, and is treated as a copy.
Other skills, from other repositories
ad-campaign-analyzer
Analyze cross-channel campaign data, quantify uncertainty, and propose evidence-labeled budget tests without overstating causality.
google-analytics
Skill "google-analytics" from VKirill/claude-lane-stack, covering version requirements (may 2026), usage, use this skill when, do not use this skill when and purpose.
google-tag-manager
Skill "google-tag-manager" from VKirill/claude-lane-stack, covering 🎯 version requirements (june 2026), usage, use this skill when, do not use this skill when and purpose.
analyzing-windows-lnk-files-for-artifacts
Parse Windows LNK shortcut files to extract target paths, timestamps, volume information, and machine identifiers for forensic timeline reconstruction.
openapi-designer
Design complete OpenAPI 3.1 specifications for RESTful APIs. Covers schemas, security, examples, webhooks, and documentation generation.
laravel-api
Build production-ready RESTful APIs with Laravel. Covers authentication (Sanctum/Passport), versioning, resources, rate limiting, and API testing.