KhazP/vibe-coding-prompt-template is a collection of templates and workflows that use large language models to turn an idea into a product requirements document, technical design, and minimum viable product plan. It is for people building MVPs with AI coding agents or chat tools, and its catalogue entries support that planning and coding workflow.
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 KhazP/vibe-coding-prompt-template --skill vibe-workflowgit clone --depth 1 https://github.com/KhazP/vibe-coding-prompt-templateWrote 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/khazp/vibe-coding-prompt-template/vibe-workflow)<a href="https://agentmods.dev/skills/khazp/vibe-coding-prompt-template/vibe-workflow"><img src="https://agentmods.dev/badge/skills/khazp/vibe-coding-prompt-template/vibe-workflow.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 120 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00059 | $0.01668 |
| Opus 5 | $0.00030 | $0.00834 |
| Sonnet 5 | $0.00012 | $0.00334 |
| Haiku 4.5 | $0.00006 | $0.00167 |
Grade A, and why
vibe-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 8d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe-Coding Workflow
You are the master orchestrator for the vibe-coding workflow. Guide users through all 5 steps to transform their idea into a working MVP.
The 5-Step Workflow
Idea -> Research -> PRD -> Tech Design -> Agent Config -> Build MVP / AI App
(20 min) (15 min) (15 min) (10 min) (1-3 hrs)
Global Rules
- Keep users in one continuous project session where possible.
- Prefer compaction/summaries over opening empty replacement chats.
- Use model family naming in guidance unless the user explicitly requests version pinning.
- Verify pricing, quotas, model names, beta features, and vendor-specific agent capabilities against official docs.
- Treat product AI and internal automation as first-class possible outputs, not afterthoughts.
- Treat AI safety, provider retention/training settings, tool permissions, evals, telemetry, cost ceilings, and builder exit plans as design-time requirements.
Interview Rules
- Use your native question tool (e.g. AskUserQuestion in Claude Code) to ask questions when available; otherwise ask in plain chat.
- Ask one question at a time by default: ask, wait for the answer, then continue.
- If the user answers several questions at once, accept those answers, skip the questions they covered, and carry on with the ones still open. Never re-ask something they already told you.
- If the user says "I don't know" or seems unsure, propose a sensible default and ask them to confirm it rather than leaving the answer blank.
- Never invent an answer they did not give. If a reply is vague, ask one short follow-up.
- Cover every question in the lists below — but let the user's own answers, and anything a
## Handoff Contextblock already supplies, close them out.
Step 1: Assess Current State
First, check what already exists in the project:
| File | Status | What It Means |
|---|---|---|
docs/research-*.md (or *.txt) |
Check | Research complete |
docs/PRD-*.md |
Check | Requirements defined |
docs/TechDesign-*.md |
Check | Architecture planned |
AGENTS.md |
Check | Ready to build |
src/ or app/ |
Check | Building started |
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.
- 8d ago First seen · 198 lines · 59 tokens per session scan A 86c6ef38362e
vibe-workflow is a skill published in the GitHub repository KhazP/vibe-coding-prompt-template (3,050 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 1,668 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
memstack-business-client-onboarding
Use this skill when the user says 'client onboarding', 'new client', 'onboard client', 'kickoff meeting', 'intake form', 'welcome email', or needs welcome sequences, questionnaires, and setup checklists for new clients. Do NOT use for contracts or invoicing.
memstack-product-mvp-scoper
Use this skill when the user says 'MVP', 'minimum viable product', 'scope the MVP', 'what should I build first', 'strip to core', or needs to define the smallest build that validates a product hypothesis. Do NOT use for full PRDs or roadmap planning.
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.
memstack-product-user-story-generator
Use this skill when the user says 'user stories', 'write stories', 'backlog', 'sprint planning', 'acceptance criteria', or needs prioritized stories with Given/When/Then criteria and story point estimates. Do NOT use for full PRDs or detailed feature specs.
memstack-marketing-marketplace-submit
Use when the user says 'submit to marketplace', 'publish my skill', 'share this skill', 'list on marketplace', 'submit plugin', 'publish to community', or needs to submit a skill or plugin to a community marketplace via PR. Do NOT use for building skills or writing plugin code.
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.