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-handoffgit 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-handoff)<a href="https://agentmods.dev/skills/khazp/vibe-coding-prompt-template/vibe-handoff"><img src="https://agentmods.dev/badge/skills/khazp/vibe-coding-prompt-template/vibe-handoff/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/khazp/vibe-coding-prompt-template/vibe-handoff"><img src="https://agentmods.dev/badge/skills/khazp/vibe-coding-prompt-template/vibe-handoff.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.00022 | $0.00174 |
| Opus 5 | $0.00011 | $0.00087 |
| Sonnet 5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
vibe-handoff 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 yesterday.
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 Handoff
Inspect the current branch/revision, working-tree changes, MEMORY.md, manifest, decisions, and available check results. Write a compact handoff with objective, current state, changed files, decisions and rationale, blockers, actual checks with date/results, unperformed checks, recovery checkpoint, and the next bounded action.
Reference product documents instead of duplicating them. Exclude secrets, credentials, personal data unnecessary for continuation, and full transcripts. Do not infer successful checks or commit uncommitted changes. Keep stable rules in AGENTS.md and replace stale progress in MEMORY.md rather than appending an unlimited log.
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.
- yesterday First seen · 12 lines · 22 tokens per session scan A 99ddf03299e6
vibe-handoff is a skill published in the GitHub repository KhazP/vibe-coding-prompt-template (3,066 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 174 once invoked, about $0.0001 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-09-10.
Other skills, from other repositories
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
project-butler
A project-memory workflow that keeps a code project’s rules, current structure, documents, logs, tasks, and handoff notes organized.
atlas-sync
Restore project context after clear/new session by following the canonical sync command doc.
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
moai-foundation-context
Manages context window optimization, session state persistence, and token budget allocation for multi-agent workflows. Use for token budget management, context limits, or session handoff across agents.