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 commands/fergupa/claude_plugins/email-sequencegit clone --depth 1 https://github.com/fergupa/claude_pluginsWrote 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/fergupa/claude_plugins/email-sequence)<a href="https://agentmods.dev/commands/fergupa/claude_plugins/email-sequence"><img src="https://agentmods.dev/badge/commands/fergupa/claude_plugins/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.00017 | $0.02322 |
| Opus 5 | $0.00009 | $0.01161 |
| Sonnet 5 | $0.00003 | $0.00464 |
| Haiku 4.5 | $0.00002 | $0.00232 |
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 — 220 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 and draft complete email sequences with full copy, timing, branching logic, and performance benchmarks for any lifecycle or campaign use case.
Trigger
User runs /email-sequence or asks to create, design, build, or draft an email sequence, drip campaign, nurture flow, or onboarding series.
Inputs
Gather the following from the user. If not provided, ask before proceeding:
-
Sequence type — one of:
- Onboarding
- Lead nurture
- Re-engagement
- Product launch
- Event follow-up
- Upgrade/upsell
- Win-back
- Educational drip
-
Goal — what the sequence should achieve (e.g., activate new users, convert leads to customers, reduce churn, drive event attendance, upsell to a higher tier)
-
Audience — who receives this sequence, what stage they are at, and any relevant segmentation details (role, industry, behavior triggers, lifecycle stage)
-
Number of emails (optional) — if not specified, recommend a count based on the sequence type using the templates in the Sequence Type Templates section below
-
Timing/cadence preferences (optional) — desired spacing between emails (e.g., "every 3 days", "weekly", "aggressive first week then taper off")
-
Brand voice — if configured in local settings, apply automatically and inform the user. If not configured, ask: "Do you have brand voice guidelines I should follow? If not, I'll use a clear, conversational professional tone."
-
Additional context (optional):
- Specific offers, discounts, or incentives to include
- CTAs or landing pages to link to
- Content assets available (blog posts, case studies, videos, guides)
- Product features to highlight
- Competitor differentiators to reference
Process
1. Sequence Strategy
Before drafting any emails, define the overall sequence architecture:
- Narrative arc — what story does this sequence tell across all emails? What is the emotional and logical progression from first email to last?
- Journey mapping — map each email to a stage of the buyer or user journey (awareness, consideration, decision, activation, expansion)
- Escalation logic — how does the intensity, urgency, or value of each email build on the previous one?
- Success definition — what specific action signals that the sequence has done its job and the recipient should exit?
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 · 220 lines · 17 tokens per session scan A 2714b0d8cce6
email-sequence is a command published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 2,322 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.