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 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/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/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="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.00144 | $0.02022 |
| Opus 5.5 | $0.00058 | $0.00809 |
| Sonnet 5.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 1mo 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.
- 1mo 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 23d ago), licensed MIT. It adds 144 tokens to every session and 2,022 once invoked, about $0.0006 per session on Opus 5.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
creative-commons-explainer
Explains a specific Creative Commons licence in plain language, telling a media professional exactly what they can and cannot do with the licensed content — including attribution requirements, commercial use rules, and derivative work restrictions.
understand-explain
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase.
founder-coach
Personal leadership development for founders and first-time CEOs. Covers founder archetype identification, delegation frameworks, energy management, CEO calendar audits, leadership style evolution, blind spot identification, imposter syndrome, founder mental health, and succession planning. Use when a founder feels…
baoyu-comic
A tool for creating original educational comics that explain knowledge or ideas through multiple illustrated panels. It supports different art styles and tones and can create several comics in one batch.
eli5
WHAT: Explains a codebase, a folder, a feature, a command or a pull request to someone who knows nothing about it, as a PR Lens canvas whose walkthrough builds the picture one part at a time. WHEN: /eli5 , or asked to explain code simply, for a beginner, a new hire, a non-engineer, or 'like I'm five'. KEYWORDS: eli5…
explorer-pipeline
Use when asked to make an interactive 3D explorer of a topic from start to finish, go from a topic to a clickable 3D learning page, or run the whole 3D explorer process. Produces a staged run of explorer-interface-brief, model-prompt-pack and explorer-viewer-builder in order for one topic, with the hand-offs between…