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 mracal/vibe-engineering --skill handover-docgit clone --depth 1 https://github.com/mracal/vibe-engineeringWrote 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/mracal/vibe-engineering/handover-doc)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/handover-doc"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/handover-doc/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/mracal/vibe-engineering/handover-doc"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/handover-doc.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.00035 | $0.00528 |
| Opus 5.5 | $0.00014 | $0.00211 |
| Sonnet 5.5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
vibe-handover-doc 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 1mo 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.
This is a copy
100% identical to vibe-handover-doc — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
vibe-handover-doc
Long sessions produce context that dies when the session ends. Capture it before it's lost.
When to Use This Skill
- End of a long development session (2+ hours of work)
- Switching context to a different project/feature
- Before taking a break on multi-session work
- When you realize "this is going to take another session"
- User says "let's continue tomorrow" or "save progress"
When NOT to Use This Skill
- Short sessions with trivial tasks
- Work that's fully committed and tested (the code IS the handover)
- When a handover doc already exists and is current
Steps
-
Capture current state:
- What branch are we on?
- What files were modified? (git status)
- Are there uncommitted changes?
- What tests are passing/failing?
-
Document completed work:
- What was accomplished this session?
- Key decisions made (reference
vibe-decision-journalentries) - Problems solved and how
-
Document remaining work:
- What's left to do?
- What's blocked and on what?
- Known issues introduced
-
Create a resume prompt:
- A specific prompt that the next session can use to get up to speed quickly
- Include: branch name, key files to read, next task to tackle
-
Save to project docs (e.g.,
docs/HANDOVER.mdordocs/handover/YYYY-MM-DD.md)
Output Format
Handover: [Feature/Project Name]
Date: [Today] Branch: [branch name]
Completed This Session
- [Task 1]
- [Task 2]
Remaining Work
- [Task 3] — [notes]
- [Task 4] — blocked by [X]
Key Decisions Made
- [Decision 1] — [rationale]
Known Issues
- [Issue 1] — [impact]
Files Changed
[git status summary]
Resume Prompt
[A specific prompt to use when resuming this work in a new session. Include context, branch, and next steps.]
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.
- 1mo ago First seen · 76 lines · 35 tokens per session scan A fd9ef2f3a024
vibe-handover-doc is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed 11d ago), licensed MIT. It adds 35 tokens to every session and 528 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-handover-doc, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
studio-context-brief
Use when an active KIT-managed Goal needs compact brief, working, or resume context projections from trusted structured state while preserving exact technical literals and durable handoff authority.
agent-v3-memory-specialist
Agent skill for v3-memory-specialist - invoke with $agent-v3-memory-specialist.
agent-swarm-memory-manager
Agent skill for swarm-memory-manager - invoke with $agent-swarm-memory-manager.
agent-collective-intelligence-coordinator
Agent skill for collective-intelligence-coordinator - invoke with $agent-collective-intelligence-coordinator.
agent-memory-coordinator
Agent skill for memory-coordinator - invoke with $agent-memory-coordinator.
memory-management
AgentDB memory system with HNSW vector search. Provides 150x-12,500x faster pattern retrieval, persistent storage, and semantic search capabilities for learning and knowledge management. Use when: need to store successful patterns, searching for similar solutions, semantic lookup of past work, learning from previous…