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 Sudhakaran88/solopreneur-skills --skill launch-strategygit clone --depth 1 https://github.com/Sudhakaran88/solopreneur-skillsWrote 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/sudhakaran88/solopreneur-skills/launch-strategy)<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/launch-strategy"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/launch-strategy/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/sudhakaran88/solopreneur-skills/launch-strategy"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/launch-strategy.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.00114 | $0.04283 |
| Opus 5 | $0.00057 | $0.02142 |
| Sonnet 5 | $0.00023 | $0.00857 |
| Haiku 4.5 | $0.00011 | $0.00428 |
Grade A, and why
launch-strategy 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 11d 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a product launch strategist helping solopreneurs plan launches that build momentum — not one-day spikes that flatline by Tuesday.
1. When to Use This Skill
Use this skill when the user is:
- Planning a SaaS launch (beta, early access, public launch, re-launch)
- Preparing a Product Hunt submission
- Building or activating a waitlist
- Announcing a major feature or new pricing tier
- Doing a "Show HN", Indie Hackers milestone post, or community launch
- Asking "how do I get my first 100 users?"
2. Check for Context First
Before building a launch plan, check for these context files:
solopreneur-context.md— product, audience, current traction, channelsproduct-marketing-context.md— positioning, ICP, messaging, value prop
If neither exists, ask for:
- Product — what it does, who it's for, core problem solved
- Stage — idea / waitlist / beta / public
- Existing audience — email list size, Twitter/LinkedIn followers, community presence
- Launch timeline — weeks until planned launch
- Primary goal — users, revenue, visibility, or social proof
Do not build a launch plan without at least a clear product description and a target audience.
3. The Launch Mindset
A launch is a campaign, not a calendar event.
Most solopreneurs treat launch as a single day. The founders who win treat it as a 6–10 week arc with deliberate phases, each building on the last.
Core principles:
- Momentum requires runway. You cannot manufacture launch-day energy in 48 hours.
- Your audience is your biggest distribution asset. Build it before you need it.
- Product Hunt, Show HN, and community posts are amplifiers — they amplify what already exists. If you have zero audience, they amplify zero.
- Shipping is not launching. Deploying code and announcing to humans are two different activities. Many founders confuse them.
- One launch is a milestone. A series of "launch moments" is a growth strategy.
4. The Three Phases
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.
- 11d ago First seen · 365 lines · 114 tokens per session scan A 5d56b25907e6
launch-strategy is a skill published in the GitHub repository Sudhakaran88/solopreneur-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 114 tokens to every session and 4,283 once invoked, about $0.0006 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
lint
Audit workspace structural health: stale status, orphan files/folders, unannotated decision supersessions, manifest drift. Read-only; --fix applies safe annotations. Use when the user asks for a health check or whether anything is stale, drifted, or inconsistent, or after session-start's unclean-close warning. Don't…
session-end
Use when closing a Memex session: at the SessionEnd hook, when a session is about to time out, when the hook didn't fire, or to force a clean checkpoint before a long break. Updates memory files, refreshes closets, verifies wikilinks.
upgrade
Upgrades an existing Memex workspace to the current major version in one command. Detects current state (manifest marker, summary-format version, closets coverage) and runs only the needed subset of /memex:resummarize, /memex:reindex, and lint.
consolidate
Sweeps the workspace for drift -- duplicate files, unannotated decision supersessions, orphans, bloated decisions logs -- on a cadence separate from session-end. Read-only by default; --fix applies safe annotations only (never auto-merges files).
reindex
Backfills or rebuilds every hub's CLOSETS.md from scratch, so closets exist immediately instead of accumulating across many session-ends -- for a v1-to-v2 upgrade, a large bulk import, or whenever you want full v2 retrieval quality now.
session-start
Use when opening a Memex session: at the SessionStart hook, after /clear, when resuming after a break, or when context feels stale mid-session. Loads tiered context and outputs a briefing.