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/classicchins/compounding-marketing/cm-emailgit 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.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.00000 | $0.04353 |
| Opus 5 | $0.00000 | $0.02176 |
| Sonnet 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 5d 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.
- 5d 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 (7 stars, last pushed 3mo 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.
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.