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 rules/rajitsaha/100xprism/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/rules/rajitsaha/100xprism/email-sequence)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/email-sequence"><img src="https://agentmods.dev/badge/rules/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 | $0.00030 | $0.01833 |
| Opus 5 | $0.00015 | $0.00916 |
| Sonnet 5 | $0.00006 | $0.00367 |
| Haiku 4.5 | $0.00003 | $0.00183 |
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 yesterday.
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 — 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 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.
- yesterday First seen · 207 lines · 30 tokens per session scan A 62c518fc7007
email-sequence is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 1,833 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-09-03.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.