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 kornpng/web-mvp-blueprint-kit --skill mvp-workflowgit clone --depth 1 https://github.com/kornpng/web-mvp-blueprint-kitWrote 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/kornpng/web-mvp-blueprint-kit/mvp-workflow)<a href="https://agentmods.dev/skills/kornpng/web-mvp-blueprint-kit/mvp-workflow"><img src="https://agentmods.dev/badge/skills/kornpng/web-mvp-blueprint-kit/mvp-workflow/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/kornpng/web-mvp-blueprint-kit/mvp-workflow"><img src="https://agentmods.dev/badge/skills/kornpng/web-mvp-blueprint-kit/mvp-workflow.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.00055 | $0.00496 |
| Opus 5 | $0.00028 | $0.00248 |
| Sonnet 5 | $0.00011 | $0.00099 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
mvp-workflow 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.
What it actually says
MVP Workflow
Guide the user through the full Web MVP Blueprint workflow.
Workflow
- Idea Brief - clarify the first user, problem, smallest useful outcome, and MVP boundary.
- Evidence Research - collect competitor, user, pricing, and feasibility evidence.
- Buildable PRD - define pages, features, data objects, acceptance criteria, and success metrics.
- Technical Blueprint - choose a practical stack and implementation route.
- Agent Context - generate
AGENTS.mdandagent_docs/. - Build Tickets - generate task files that Codex can execute one at a time.
State Check
Inspect the current project before choosing the next step:
| Artifact | Meaning |
|---|---|
docs/IdeaBrief-*.md |
Step 0 complete |
docs/EvidencePack-*.md |
Step 1 complete |
docs/BuildablePRD-*.md |
Step 2 complete |
docs/TechBlueprint-*.md |
Step 3 complete |
AGENTS.md and agent_docs/ |
Step 4 complete |
tasks/*.md |
Step 5 complete |
Routing
- If no idea brief exists, use
$mvp-idea-brief. - If idea brief exists but no evidence pack exists, use
$mvp-research. - If evidence exists but no buildable PRD exists, use
$mvp-prd. - If PRD exists but no technical blueprint exists, use
$mvp-tech-design. - If technical blueprint exists but no agent context exists, use
$mvp-agent-context. - If agent context exists but no task tickets exist, use
$mvp-build-tickets.
Rules
- Keep the user oriented with the current step and next artifact.
- Ask one question at a time when inputs are missing.
- Favor small Web MVP scope over broad product ambition.
- Preserve explicit "Not in MVP" decisions.
- Do not start implementation until agent context and tickets exist, unless the user explicitly skips planning.
What ships with it
1 file 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.
- 11d ago First seen · 48 lines · 55 tokens per session scan A 7b2dbefc7fc2
mvp-workflow is a skill published in the GitHub repository kornpng/web-mvp-blueprint-kit (23 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 496 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
pitch-deck
Use when building or fixing an investor fundraising deck — the narrative arc, the slide-by-slide story, and the few numbers that actually move an investment decision, for a pre-seed, seed or Series A raise (or an accelerator application deck). Decides what goes on each slide, in what order, with which metric…
no-code-app
Use when building an app on a no-code/low-code platform (Bubble, Softr, Glide over Airtable or Xano) — picking the platform, modeling the data, keeping usage-metered cost predictable, and planning the exit before lock-in. NOT a hand-written coded app (that is nextjs), NOT wiring SaaS tools together with no app UI…
ai-product-launch
First AI Product Launch — Zero to Live in 30 Days. Step-by-step guide for shipping your first AI product from idea validation to paying customers. Includes day-by-day timeline and real examples. By @WeiYipei.
ai-delivery-spec
Clarify, create, review or change product, service and office workflow requirements, PRDs and interactive prototypes. Use for vague goals, process improvements, spreadsheet/form rules, small UI edits and changes to existing systems, even without the word requirement.…
vibe-coding-prd
An interview-style requirements assistant that turns an unclear product idea into a practical product requirements document, or PRD. A PRD explains what a product should do well enough for development to begin.
vibe-coding-requirements
A requirements guide for using AI to build software from an idea, including demos and longer-term products. It helps describe what should happen, who it is for, and the limits of the work.