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.
git clone --depth 1 https://github.com/classicchins/compounding-marketingWrote 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/classicchins/compounding-marketing/cm-email)<a href="https://agentmods.dev/commands/classicchins/compounding-marketing/cm-email"><img src="https://agentmods.dev/badge/commands/classicchins/compounding-marketing/cm-email/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/classicchins/compounding-marketing/cm-email"><img src="https://agentmods.dev/badge/commands/classicchins/compounding-marketing/cm-email.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.00000 | $0.04353 |
| Opus 5.5 | $0.00000 | $0.01741 |
| Sonnet 5.5 | $0.00000 | $0.00871 |
| Haiku 4.5 | $0.00000 | $0.00435 |
Grade A, and why
cm-email 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 2mo 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 — 567 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cm:email — Email Campaign Setup End-to-End
Plan and execute a complete email campaign from audience selection to delivery, with optimization frameworks and success metrics.
What It Does
Walks you through email campaign creation: choosing campaign type, segmenting audience, writing subject lines, structuring copy, optimizing send times, and measuring results.
Process
Step 1: Campaign Type Selection
Choose the campaign type that matches your goal:
1. Announcement (New Product/Feature Launch)
Goal: Inform existing audience about something new
Audience: Customers + engaged leads
Send: One-time broadcast
Key Elements:
- What's new
- Why it matters (benefit, not feature)
- Clear CTA (try it, learn more, upgrade)
Example:
- Subject: "Introducing [Feature]: Now You Can [Benefit]"
- Body: Problem → Solution (new feature) → How to use it → CTA
2. Nurture (Multi-Touch Educational Series)
Goal: Build trust, educate, move prospects down funnel
Audience: MQLs, trial users, engaged subscribers
Send: Sequence (3-7 emails over days/weeks)
Key Elements:
- Value-first (education > selling)
- Progressive disclosure (start broad, get specific)
- Soft CTAs (learn more, not "buy now")
Example Series:
- Email 1: "The Problem with [Current Approach]"
- Email 2: "A Better Way: [Framework]"
- Email 3: "How [Customer] Solved This"
- Email 4: "Try It Yourself: [Product Demo]"
3. Re-Engagement (Win Back Inactive Users)
Goal: Revive cold leads or dormant customers
Audience: No email opens in 60-90 days OR no product login in 30+ days
Send: 2-4 email sequence
Key Elements:
- Acknowledge absence ("We miss you")
- Provide value (what's new since they left)
- Incentive (optional: discount, extended trial)
- Easy out (unsubscribe option — clean your list)
Example Series:
- Email 1: "We noticed you've been away"
- Email 2: "Here's what you missed" (product updates, new content)
- Email 3: "Last chance: [Incentive]"
- Email 4: "Should we say goodbye?" (final opt-in confirmation)
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.
- 2mo ago First seen · 567 lines · 0 tokens per session scan A b82f2db08fab
cm-email is a command published in the GitHub repository classicchins/compounding-marketing (8 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,353 tokens. 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-31.
cm-email compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| cm-emailclassicchins/compounding-marketing | Command | 8 | 5mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |