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 agentmods add skills/ash1794/vibe-engineering/handover-docnpx skills add ash1794/vibe-engineering --skill handover-docgit clone --depth 1 https://github.com/ash1794/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/ash1794/vibe-engineering/handover-doc)<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/handover-doc"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/handover-doc.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.00035 | $0.00528 |
| Opus 5 | $0.00017 | $0.00264 |
| Sonnet 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vibe-handover-doc — 100% identical, 0 lines differ
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.
- 6d ago First seen · 76 lines · 35 tokens per session scan A fd9ef2f3a024
vibe-handover-doc is a skill published in the GitHub repository ash1794/vibe-engineering (10 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 528 once invoked, about $0.0002 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-31.
Other skills, from other repositories
wechat-article-writer
公众号/自媒体全流程。根据用户表述自动匹配：撰写文章、封面图、正文插图、风格提取。支持多种写作风格。当用户提到写公众号、技术博客、公众号封面、正文插图、步骤图、演示图、流程示意、分析写作风格、克隆文风、模仿爆款、提取风格时使用。详见 reference 目录。.
prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
cherry-assistant-guide
从当前安装包查询 Cherry Studio 产品信息并排查运行问题。当用户询问功能、路由、快捷键、Provider、语言、Agent、频道、定时任务、Code CLI、当前版本，或报告运行错误、连接失败、配置异常并需要诊断时触发。.
cherry-electron-dev
Develop, fix, and profile Cherry Studio in a tracked Electron instance. Use for everyday implementation, UI and interaction work, bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis; reuse a verified workspace instance…
issue-reporter
只在用户明确要求提交 GitHub Issue、GitHub Bug Report 或 GitHub Feature Request 时使用。用户只说“提交问题”“提交反馈”“上报 bug”“这是个 bug”或描述功能建议但未点名 GitHub 时不得触发，必须改用 cherry-studio-feedback 并默认提交飞书。.