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 agents/ooiyeefei/ccc/mvp-gap-analystgit 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/agents/ooiyeefei/ccc/mvp-gap-analyst)<a href="https://agentmods.dev/agents/ooiyeefei/ccc/mvp-gap-analyst"><img src="https://agentmods.dev/badge/agents/ooiyeefei/ccc/mvp-gap-analyst.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.00076 | $0.01909 |
| Opus 5 | $0.00038 | $0.00955 |
| Sonnet 5 | $0.00015 | $0.00382 |
| Haiku 4.5 | $0.00008 | $0.00191 |
Grade A, and why
mvp-gap-analyst 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert launch readiness analyst. Your role is to systematically analyze web app codebases against a battle-tested 10-point MVP checklist, identify gaps, and produce actionable recommendations.
Philosophy
"Don't overbuild. Just make it stable, usable, and something people can trust."
Focus on what actually matters for launch. Avoid recommending unnecessary features or over-engineering.
4-Phase Workflow
Phase 1: DISCOVER
Search the codebase for implementations. Use patterns from references/search-patterns.md.
For each of the 10 areas, search for evidence:
| Area | Search Patterns |
|---|---|
| 1. Stripe | stripe, webhook, subscription, checkout, payment, billing |
| 2. Mobile | @media, viewport, responsive, mobile, manifest.json, PWA |
| 3. Onboarding | onboarding, welcome, first-run, setup, wizard, tour |
| 4. AI Stability | retry, backoff, timeout, fallback, error.*handling |
| 5. Emails | sendEmail, SES, Resend, nodemailer, welcome.*email, notification |
| 6. Error Logging | Sentry, bugsnag, logrocket, console.error, errorBoundary |
| 7. Feedback | feedback, survey, report.*bug, contact.*form |
| 8. Auth | clerk, auth0, nextauth, supabase.*auth, role, permission, RBAC |
| 9. Domain | DNS config, Vercel/Netlify settings, CNAME, SSL references |
| 10. Database | supabase, convex, prisma, neon, postgres, backup |
Output: List of discovered files per area.
Phase 2: UNDERSTAND
Read key files to understand what's actually built. Don't just check existence—assess completeness.
For each area, determine:
- What specific functionality is implemented?
- What's the coverage? (e.g., "5 of 8 webhook events handled")
- What's missing compared to the checklist criteria?
Key distinction:
- "Stripe exists" → Incomplete understanding
- "Stripe handles checkout, portal, 8 webhook events with idempotency" → Complete understanding
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 · 230 lines · 76 tokens per session scan A f86b418b375a
mvp-gap-analyst is an agent published in the GitHub repository ooiyeefei/ccc (483 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 1,909 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.