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-prdgit 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-prd)<a href="https://agentmods.dev/skills/kornpng/web-mvp-blueprint-kit/mvp-prd"><img src="https://agentmods.dev/badge/skills/kornpng/web-mvp-blueprint-kit/mvp-prd/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-prd"><img src="https://agentmods.dev/badge/skills/kornpng/web-mvp-blueprint-kit/mvp-prd.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.00056 | $0.00249 |
| Opus 5 | $0.00028 | $0.00125 |
| Sonnet 5 | $0.00011 | $0.00050 |
| Haiku 4.5 | $0.00006 | $0.00025 |
Grade A, and why
mvp-prd 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 12d 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 PRD
Create docs/BuildablePRD-[AppName].md.
Inputs
Read:
docs/IdeaBrief-*.mddocs/EvidencePack-*.md
Ask one question at a time for missing product name, target user, core journey, must-have features, exclusions, success metrics, key screens, data objects, design direction, and privacy constraints.
Output
The PRD must include:
- Product overview
- Problem and promise
- User journey
- Information architecture
- P0/P1/not-in-MVP features
- Acceptance criteria for every P0 feature
- Data model draft
- Success metrics
- Design direction
- Risks and assumptions
- Definition of Done
Rules
- No vague feature names without actions and data.
- Every P0 feature must be testable.
- Move complex or uncertain ideas to "Not in MVP".
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.
- 12d ago First seen · 40 lines · 56 tokens per session scan A a5a66ccd0048
mvp-prd is a skill published in the GitHub repository kornpng/web-mvp-blueprint-kit (23 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 249 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
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…
vibe-coding-survival
A practical guide for managing projects built with AI that writes code, often called vibe coding. It covers keeping decisions recorded, limiting the work in progress, saving usable versions, and checking that changes really work.
requirement-delivery
A workflow for turning a new software request into a small, working deliverable. It clarifies acceptance criteria, identifies boundaries, breaks work into demonstrable parts, and looks for existing code or tools to reuse.
gh-issues
Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via gh. Covers issue templates, project board assignment, title conventions, and required gh scopes.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.