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/ooiyeefei/ccc/mvp-launchnpx skills add ooiyeefei/ccc --skill mvp-launchgit clone --depth 1 https://github.com/ooiyeefei/cccWrote 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/ooiyeefei/ccc/mvp-launch)<a href="https://agentmods.dev/skills/ooiyeefei/ccc/mvp-launch"><img src="https://agentmods.dev/badge/skills/ooiyeefei/ccc/mvp-launch.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.00073 | $0.01071 |
| Opus 5 | $0.00036 | $0.00535 |
| Sonnet 5 | $0.00015 | $0.00214 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
mvp-launch 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MVP Launch Checklist
A battle-tested 10-point checklist for web app MVP launches. Based on building 30+ apps.
Philosophy: "Don't overbuild. Just make it stable, usable, and something people can trust."
The 10-Point Checklist
1. Stripe Setup (Payment Infrastructure)
What counts as DONE:
- Trials configured with appropriate period
- Plan switching works (upgrade/downgrade)
- Failed payment handling with retry logic
- Webhook endpoint registered in Stripe Dashboard
- Live keys tested (not just test mode)
Required Webhook Events:
customer.subscription.trial_will_endcustomer.subscription.createdcustomer.subscription.updatedcustomer.subscription.deletedinvoice.payment_succeededinvoice.payment_failedinvoice.createdcheckout.session.completed
Verification: See references/stripe-testing.md
2. Mobile-First Design
What counts as DONE:
- Tested on real phones (not just browser resize)
- Touch targets appropriately sized (44x44px minimum)
- Forms work on mobile keyboards
- No horizontal scroll on mobile
Key insight: Browser resize mode lies. Real device testing is mandatory.
Bonus (not required):
- PWA manifest for installability
- Offline capability for core features
3. Smooth Onboarding
What counts as DONE:
- Steps kept minimal (3-5 max)
- Users guided to a fast first win
- Progress indicator if multi-step
- Can be skipped/completed later
Anti-pattern: Don't require 10 fields before users see value.
4. AI & Automation Stability
What counts as DONE:
- API errors handled gracefully
- Retry logic with exponential backoff
- Edge cases don't crash the app
- Timeouts configured appropriately
- Fallback behavior when AI fails
Good defaults:
- 3 retry attempts
- 30-60s timeout for complex operations
- User-friendly error messages
5. Critical Emails
What counts as DONE:
- Welcome email (immediate after signup)
- Trial-ending email (before trial expires)
- Failed payment email (when charge fails)
- Password reset (if not using external auth)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 178 lines · 73 tokens per session scan A 799216d7c151
mvp-launch is a skill published in the GitHub repository ooiyeefei/ccc (484 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 1,071 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…