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/skillmedev/course-creator-launch-system/launch-email-sequencenpx skills add SkillMedev/course-creator-launch-system --skill launch-email-sequencegit clone --depth 1 https://github.com/SkillMedev/course-creator-launch-systemWrote 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/skillmedev/course-creator-launch-system/launch-email-sequence)<a href="https://agentmods.dev/skills/skillmedev/course-creator-launch-system/launch-email-sequence"><img src="https://agentmods.dev/badge/skills/skillmedev/course-creator-launch-system/launch-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.00144 | $0.02022 |
| Opus 5 | $0.00072 | $0.01011 |
| Sonnet 5 | $0.00029 | $0.00404 |
| Haiku 4.5 | $0.00014 | $0.00202 |
Grade A, and why
launch-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 4d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Email Sequence
An open-cart launch lives or dies on two things most creators get backward: the selling happens mostly before the cart opens, and 40 to 50 percent of sales land in the last 48 hours no matter how good the early emails are. Creators who skip the runway launch to a cold list, and creators who go quiet near the deadline - afraid of "too many emails" - leave half the revenue unsent. This skill builds both halves: the 2-3 week runway that seeds the problem, and the day-by-day cart sequence that serves the deadline instead of faking one.
This skill runs after course-outline-architect (the transformation statement is the campaign's spine) and in lockstep with course-sales-page - every email quotes that page's promise, value stack, and guarantee word-for-word, because a mismatch between email and page is where trust dies at the moment of purchase.
Worked example throughout: Dana, 8,000-subscriber list, launching "Notion OS for Consultants" at $297.
Operating procedure
Step 1: Collect the inputs
- List size, recent open and click rates. Label estimates as estimates.
- The transformation statement and module milestones from course-outline-architect.
- The sales page URL, value stack, and guarantee wording from course-sales-page.
- Cart window (default 6 days) and the real reason the deadline exists (Step 5 requires one).
- Proof assets: results, screenshots, early-student wins.
Set expectations with the math: a well-run launch to a warm list converts 1 to 2 percent of the list. Dana at 8,000 subscribers plans on roughly 120 sales at $297 - about $35,600 - and treats anything from 80 to 160 as normal variance, not success or failure.
Step 2: Build the pre-launch runway (2-3 weeks, no selling)
Three weekly value emails (or two weeks if the list is very warm) that make the problem vivid and the mechanism credible before anything is for sale. Each teaches something genuinely useful and seeds one launch theme:
- Runway 1 - name the problem. Dana: "The 5-hour tax: where a consultant's week actually goes." Teaches a time audit; seeds the before state.
- Runway 2 - shift the belief. "Why another productivity app won't fix it (and what will)." Teaches that tools without a system fail; seeds the mechanism.
- Runway 3 - show the after + open loop. "Inside the system that onboards a client in under a day." A real walkthrough; ends with "next week I'm opening something for you."
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.
- 4d ago First seen · 108 lines · 144 tokens per session scan A f49d111737e1
launch-email-sequence is a skill published in the GitHub repository SkillMedev/course-creator-launch-system (1 stars, last pushed 2mo ago), licensed MIT. It adds 144 tokens to every session and 2,022 once invoked, about $0.0007 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-31.
Other skills, from other repositories
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
create-app
Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…
create-business
Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation…
improve-app
Guided journey from a shipped app that works but feels rough to a product that fits the job, flows without friction, reads clearly, and persuades honestly. Orchestrates nine skills phase by phase - jobs-to-be-done, ux-heuristics, design-everyday-things, refactoring-ui, microinteractions, made-to-stick…
clean-architecture
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go"…
cold-start-problem
Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my…