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/chacosoldier/compabob/handovernpx skills add chacosoldier/compabob --skill handovergit clone --depth 1 https://github.com/chacosoldier/compabobWrote 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/chacosoldier/compabob/handover)<a href="https://agentmods.dev/skills/chacosoldier/compabob/handover"><img src="https://agentmods.dev/badge/skills/chacosoldier/compabob/handover.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 | $0.00043 | $0.00309 |
| Opus 5 | $0.00022 | $0.00154 |
| Sonnet 5 | $0.00009 | $0.00062 |
| Haiku 4.5 | $0.00004 | $0.00031 |
Grade A, and why
handover 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 4d 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
Handover
Persist session context so the next session starts oriented instead of cold.
Steps
- Summarize the session: what was worked on, what was decided, what was finished.
- Capture the open thread: what is in progress, the exact next step, and any state that matters (a branch name, a file mid-edit, a blocked decision).
- Note anything fragile: a test that is failing, an assumption not yet verified, a thing that will break if forgotten.
- Write the note to
.tmp/handover.md. Thehook-session-start.shhook reads this file at the start of the next session and injects it automatically.
Format
# Handover — <date> <time>
## Done this session
- ...
## In progress
- [the open thread, with the exact next step]
## Watch out for
- [anything fragile or unverified]
## Next step
[one sentence: what to do first next session]
After writing, confirm in one line: "Handover saved to .tmp/handover.md." If durable facts surfaced (not session state, but lasting knowledge), also propose memory writes per the constitution.
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.
- 4d ago First seen · 36 lines · 43 tokens per session scan A db42a76e7b9a
handover is a skill published in the GitHub repository chacosoldier/compabob (32 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 309 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-30.
Other skills, from other repositories
agent-project-board-sync
Agent skill for project-board-sync - invoke with $agent-project-board-sync.
agent-issue-tracker
Agent skill for issue-tracker - invoke with $agent-issue-tracker.
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
slack-construct-agents
Standing context for Slack sibling agents — one room per team, creator-posted introductions, bot-to-bot hop discipline. Ships as instructions.md composed into the group's CLAUDE.md at spawn; there is no workflow to invoke.
status-report
Use when the user asks for a weekly / monthly status report, project update, individual or team progress summary. Produces a tight, scannable update with what shipped, what's in flight, what's blocked, and metrics.