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.
git 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/commands/khazp/vibe-coding-prompt-template/vibe-agents)<a href="https://agentmods.dev/commands/khazp/vibe-coding-prompt-template/vibe-agents"><img src="https://agentmods.dev/badge/commands/khazp/vibe-coding-prompt-template/vibe-agents.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.1 | $0.00000 | $0.00214 |
| Opus 5 | $0.00000 | $0.00107 |
| Sonnet 5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
vibe-agents 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.
What it actually says
/vibe-agents — Step 4: Agent-file setup
Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.
Read part4-notes-for-agent.md at the repository root and follow it as the single source of truth. (If it isn't in this project, ask the user to paste it.)
The essentials:
- Requires
docs/PRD-*.mdanddocs/TechDesign-*.md— if either is missing, route the user back a stage. - Instantiate the files in
templates/(AGENTS.md,MEMORY.md,REVIEW-CHECKLIST.md,agent_docs/) — fill every[REPLACE:]/[CHOOSE:]placeholder from the PRD and Tech Design; never rewrite the templates. - Add the thin tool adapter from
templates/tool-adapters/for the user's tool.
Done? Point the user to the final stage: /vibe-build.
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 · 13 lines · 0 tokens per session scan A 276043859857
vibe-agents is a command published in the GitHub repository KhazP/vibe-coding-prompt-template (3,044 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 214 tokens. 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 commands, from other repositories
prd
You're helping the user create a Product Requirements Document — the most important document before building. This defines WHAT to build, WHO it's for, and WHY it matters.
implement
You're helping the user build. Time to write code.
plan
You're helping the user plan a software project or feature.
test
Let's validate that what was built actually works.
checklist
You're helping the user break down their project into an ordered, actionable checklist.
fix
Something's broken. Let's diagnose and fix it.