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/cwinvestments/memstack/launch-plannpx skills add cwinvestments/memstack --skill launch-plangit clone --depth 1 https://github.com/cwinvestments/memstackWhat 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.00065 | $0.02810 |
| Opus 5 | $0.00032 | $0.01405 |
| Sonnet 5 | $0.00013 | $0.00562 |
| Haiku 4.5 | $0.00006 | $0.00281 |
Grade A, and why
memstack-marketing-launch-plan 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 2d 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Plan — Planning product launch...
Develops a day-by-day launch timeline with pre-launch buildup, launch week execution, post-launch optimization, channel strategy, PR outreach templates, and metrics tracking.
Activation
When this skill activates, output:
Launch Plan — Planning product launch...
Then execute the protocol below.
Context Guard
| Context | Status |
|---|---|
| User says "launch plan", "product launch", "go-to-market" | ACTIVE |
| User says "launch calendar" or "launch timeline" | ACTIVE |
| User is preparing to release a new product or feature | ACTIVE |
| User wants an ongoing sales funnel (not time-bound) | DORMANT — use Sales Funnel |
| User wants ad copy only | DORMANT — use Facebook Ad or Google Ad |
Common Mistakes
| Mistake | Why It's Wrong |
|---|---|
| "Launch day IS the marketing plan" | 80% of launch success happens in the pre-launch phase. The launch day is execution, not strategy. |
| "Tell everyone at once" | Tiered reveals (insiders → waitlist → public) create momentum and social proof. |
| "No deadline on the launch offer" | Open-ended launches have no urgency. Set a clear close date for the launch price/bonus. |
| "Skip the waitlist" | A waitlist of 500+ people means launch day revenue, not crickets. |
| "Go dark after launch day" | Post-launch follow-up (days 2-7) often generates more revenue than day 1. |
Protocol
Step 1: Gather Launch Requirements
If the user hasn't provided details, ask:
- Product/service — what are you launching? (name, description, price)
- Launch date — when does it go live?
- Audience size — email list, social followers, existing customers?
- Launch type — new product, major update, beta → GA, or seasonal promotion?
- Channels — email, social, ads, PR, partnerships, affiliates?
- Launch offer — special pricing, bonus, or early-bird deal?
Step 2: Define Launch Type & Timeline
| Launch Type | Pre-Launch | Launch Window | Post-Launch |
|---|---|---|---|
| Product Hunt launch | 2-4 weeks | 1 day | 1 week |
| SaaS launch | 4-6 weeks | 1 week | 2-4 weeks |
| Course/info product | 2-4 weeks | 3-5 days (open cart) | 1 week |
| E-commerce product | 2-3 weeks | 1-2 weeks | Ongoing |
| Feature launch | 1-2 weeks | 1-3 days | 1 week |
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.
- 2d ago First seen · 295 lines · 65 tokens per session scan A 94dfae642b99
memstack-marketing-launch-plan is a skill published in the GitHub repository cwinvestments/memstack (417 stars, last pushed 6d ago), licensed MIT. It adds 65 tokens to every session and 2,810 once invoked, about $0.0003 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
frontend-design-landing-page
Marketing landing page and conversion-focused product page reference. Use this skill when building hero sections, feature grids, pricing pages, testimonials, CTAs, footers, navigation bars, or any public-facing marketing surface. Covers a warm, professional, developer-friendly design language (cream backgrounds…
plan-ceo-review
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when…
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…