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/moizibnyousaf/marketing-cli/email-sequencesnpx skills add MoizIbnYousaf/marketing-cli --skill email-sequencesgit clone --depth 1 https://github.com/MoizIbnYousaf/marketing-cliWrote 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/moizibnyousaf/marketing-cli/email-sequences)<a href="https://agentmods.dev/skills/moizibnyousaf/marketing-cli/email-sequences"><img src="https://agentmods.dev/badge/skills/moizibnyousaf/marketing-cli/email-sequences.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.00154 | $0.04028 |
| Opus 5 | $0.00077 | $0.02014 |
| Sonnet 5 | $0.00031 | $0.00806 |
| Haiku 4.5 | $0.00015 | $0.00403 |
Grade A, and why
email-sequences 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.
How it starts
The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note: Examples below use fictional brands (Acme, Lumi, Helm). Replace with your own brand context.
Email Sequences
You build automated email flows that move people from stranger to customer. Each email earns the right to send the next one by delivering genuine value. No "just checking in" — every email has a job.
On Activation
- Read
brand/voice-profile.md— emails are the most intimate channel, voice matters most here - Read
brand/audience.md— understand awareness level, sophistication, pain points - Read
brand/positioning.md— know the product angle and differentiation - If brand files don't exist, ask: What do you sell? Who's receiving these? What action do you want them to take?
- Check
marketing/emails/for existing sequences — avoid overlap
Brand Integration
Brand files shape every email in the sequence:
- voice-profile.md → Tone across all emails. If voice is friendly/casual, open with 'Hey {{first_name}}!' and use contractions. If professional/formal, use 'Good morning {{first_name}},' and complete sentences. Voice consistency across a 7-email sequence is what builds trust.
- audience.md → Pain points drive email hooks. Each email should reference a specific pain from the persona, not generic benefits. If audience is time-starved founders, lead with efficiency. If audience is creative professionals, lead with inspiration.
- positioning.md → The unique angle appears in every CTA and subject line. Don't sell features — sell the positioning angle consistently across all emails.
Sequence Types
| Type | Trigger | Goal | Length | Timing |
|---|---|---|---|---|
| Welcome | New subscriber | Build trust, set expectations, deliver first value | 5-7 emails | Days 0, 1, 3, 5, 7, 10, 14 |
| Nurture | Post-welcome or lead magnet | Educate, build authority, warm up for offer | 5-10 emails | Every 2-3 days |
| Launch | Product launch or promotion | Create urgency, overcome objections, convert | 6-8 emails | Days -3, -1, 0, 0+6hr, 1, 3, 5, 7 |
| Onboarding | New customer/user | Activate, reduce churn, drive first success | 5-7 emails | Days 0, 1, 3, 5, 7, 14, 30 |
| Re-engagement | Inactive subscriber | Win back or clean list | 3-4 emails | Days 0, 3, 7, 14 |
What ships with it
1 file 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 · 386 lines · 154 tokens per session scan A 89089570a352
email-sequences is a skill published in the GitHub repository MoizIbnYousaf/marketing-cli (31 stars, last pushed 20d ago), licensed MIT. It adds 154 tokens to every session and 4,028 once invoked, about $0.0008 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 skills, from other repositories
linkedin-reply-handler
Draft a reply to a specific existing LinkedIn comment from its URL. Use when the user wants to reply to a comment on any post, or follow up after an author replied to them. Parses the commentUrn, resolves the correct parentComment target (LinkedIn flattens threads to 2 levels), and posts via Publora on approval. Not…
linkedin-comment-drafter
Draft a LinkedIn comment on someone else's post from its URL, or reshare (repost) it to your feed with optional commentary. Use when the user pastes a post URL and asks to comment, engage, be first commenter, or repost with their thoughts. Produces 1-3 variants in the user's voice, picks a reaction, and publishes via…
linkedin-employee-advocacy
Stand up and run a LinkedIn employee advocacy program for a marketing or sales team. Covers 14-day launch playbook, brand-guideline governance, per-post time budget, cadence benchmarks, and team ROI (reach, engagement, pipeline). Triggers on "employee advocacy", "get the team posting", "scale LinkedIn across team"…
ads-landing
Audit paid-ad landing pages for message match, mobile experience, performance, accessibility, trust, forms, consent, tracking, security, and conversion friction. Use for landing-page audit, post-click experience, LP audit, conversion-rate optimization, form optimization, ad-to-page message match, redirects, blocked…
ads-research
Refresh Claude Ads platform, API, policy, regulation, benchmark, issue, pull-request, fork, and repository evidence. Use for ads research refresh, expired refreshdue dates, stale API or platform claims, reverify-or-demote decisions, release-current claim validation, ecosystem review, current platform changes, or…
ads-amazon
Audit Amazon Ads profiles, regions, Sponsored Products, Sponsored Brands, Sponsored Display, DSP, portfolios, targeting, search terms, retail readiness, creative, budgets, ACOS, TACOS, reporting, and policy. Use for Amazon Ads, sponsored ads, Amazon PPC, ACOS, TACOS, ASIN advertising, Amazon DSP, or retail-media…