Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pronpx agentmods add commands/indranilbanerjee/digital-marketing-pro/email-sequenceWrote 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/commands/indranilbanerjee/digital-marketing-pro/email-sequence)<a href="https://agentmods.dev/commands/indranilbanerjee/digital-marketing-pro/email-sequence"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/email-sequence/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/commands/indranilbanerjee/digital-marketing-pro/email-sequence"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/digital-marketing-pro/email-sequence.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.00019 | $0.01196 |
| Opus 5 | $0.00010 | $0.00598 |
| Sonnet 5 | $0.00004 | $0.00239 |
| Haiku 4.5 | $0.00002 | $0.00120 |
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 10d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email Sequence
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Design a complete email sequence ready for implementation in any ESP. Includes subject lines with A/B variants, preview text, full body copy, send timing with cadence logic, segmentation rules, branching conditions, personalization tokens, and deliverability best practices.
Trigger
User runs /digital-marketing-pro:email-sequence or asks to create an email drip, email flow, nurture sequence, welcome series, re-engagement campaign, or cart abandonment flow.
Inputs
Gather the following from the user. If not provided, ask before proceeding:
-
Sequence type — one of:
- Welcome series (new subscriber/user)
- Nurture sequence (move leads down funnel)
- Onboarding (activate new users/customers)
- Re-engagement (win back inactive subscribers)
- Cart abandonment (recover lost purchases)
- Post-purchase (retention, upsell, review request)
- Event-based (webinar, product launch, seasonal)
- Promotional (sale, offer, limited-time)
-
Goal — what the sequence should achieve (activate, convert, retain, upsell, educate, re-engage)
-
Audience segment — who receives this sequence and what triggers entry (signup, purchase, inactivity period, cart event, etc.)
-
Number of emails — desired count, or let the system recommend based on sequence type
-
Key messages or offers — core value propositions, promotions, or content to include
-
ESP (optional) — platform in use (Klaviyo, Mailchimp, HubSpot, SendGrid, Customer.io) for format and feature guidance
Brand Voice
- If a brand profile exists, apply voice settings automatically
- Load email-specific tone overrides from guidelines if available
- Apply compliance rules (CAN-SPAM, GDPR, CASL) based on brand's target markets
Sequence Design
Sequence Architecture
- Map the sequence to the customer journey stage
- Define the narrative arc (introduction → value → proof → conversion)
- Determine optimal email count based on sequence type:
- Welcome: 3-5 emails over 7-14 days
- Nurture: 5-8 emails over 3-6 weeks
- Onboarding: 4-7 emails over 14-30 days
- Re-engagement: 3-4 emails over 7-14 days
- Cart abandonment: 3 emails over 3 days
- Post-purchase: 3-5 emails over 30-60 days
- Define send cadence and timing logic
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.
- 10d ago First seen · 135 lines · 19 tokens per session scan A c0a4334fe446
email-sequence is a command published in the GitHub repository indranilbanerjee/digital-marketing-pro (801 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 1,196 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-08-30.
Other commands, from other repositories
brand-setup
Configure brand voice, terminology, compliance guardrails, and style guide for content production.
output-folder
Print the absolute path to the user-visible ContentForge output folder and open it in the OS file manager.
create-content
Run the full 10-phase content production pipeline — research, draft, fact-check, humanize, and publish.
audit-content
Audit your content library for freshness decay, coverage gaps, and optimization opportunities.
content-brief
Generate a research-backed content brief with keyword data, competitor analysis, search intent, and SEO strategy.
publish
Publish finished content to Webflow or WordPress with preview, verification, and HTML export fallback.