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/tonydzi/second-brain-starter-kit/handoffnpx skills add tonydzi/second-brain-starter-kit --skill handoffgit clone --depth 1 https://github.com/tonydzi/second-brain-starter-kitWrote 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/tonydzi/second-brain-starter-kit/handoff)<a href="https://agentmods.dev/skills/tonydzi/second-brain-starter-kit/handoff"><img src="https://agentmods.dev/badge/skills/tonydzi/second-brain-starter-kit/handoff.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.00106 | $0.00973 |
| Opus 5 | $0.00053 | $0.00487 |
| Sonnet 5 | $0.00021 | $0.00195 |
| Haiku 4.5 | $0.00011 | $0.00097 |
Grade A, and why
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/handoff — hand the work over to another session / person / machine
When the work has to continue somewhere ELSE (another machine, another person — the operator ↔ a human assistant, or simply a fresh session after /compact), /handoff assembles one self-contained document that lets someone pick it up cold. It kills the "so what were you doing here?" round trip.
What to assemble (the /compact format — rationales are lost first, so record them verbatim)
As headings with bulleted lists:
- DECISIONS — what was decided + WHY (what was rejected; what we do / do NOT do).
- DONE + TESTS — what is finished and how it was verified (counters, exit codes, "passed/failed").
- PATHS AND VALUES — exact files/scripts/folders + values (note names, IDs, env vars, constants).
- OPEN / BLOCKERS — what is unfinished, what is broken (the symptom), what we are waiting on.
- BOUNDARIES — what NOT to touch, what needs the operator's approval (Tier-2), what is hub-only.
- ➤ CONTINUE FROM HERE — one explicit first step for whoever picks it up.
Where to put it (synced → it travels on its own)
- Machine-to-machine (Claude→Claude):
$OBSIDIAN_VAULT/_machine-bus/_transit/handoffs/HANDOFF-<latin-slug>.md(create the folder if missing). The file name is ALWAYS in Latin script (vault conventions). - For a human assistant who works from dashboards: also drop a copy into
$OBSIDIAN_VAULT/_Dashboards/HANDOFF-<slug>.md(example:_Dashboards\HANDOFF-booking-session.md). - URGENT and addressed to a specific machine → plus a ping over the bus:
python "$USERPROFILE/.claude/scripts/machine_bus.py" send <MACHINE-NAME> "handoff ready: <path>, continue from there".
Hand the operator a seed (one line to paste into the receiving session)
"Read
<path to HANDOFF-...md>and continue from there."
When to call it
- The work will be continued by another machine/person (handing over a booking, a research thread, an import).
- A long task is about to be cut (before
/compactor a machine switch) — so state is not lost. - A recurring handover between the operator and an assistant over calls/tasks = one call instead of assembling it by hand.
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.
- 5d ago First seen · 60 lines · 106 tokens per session scan A 8eeea1dd5b5e
handoff is a skill published in the GitHub repository tonydzi/second-brain-starter-kit (5 stars, last pushed 5d ago), licensed MIT. It adds 106 tokens to every session and 973 once invoked, about $0.0005 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
wiki-ingest
Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this…
autoresearch
Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find…
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
canvas
Create, inspect, and update Obsidian JSON Canvas boards with text, file, link, group, and edge nodes. Use for canvas status, canvas lists, visual maps, zones, spatial layouts, adding vault notes or media to a .canvas file, and requests such as create canvas, add to canvas, or put this on the canvas.
defuddle
Plan and, with explicit network consent, use an optional external Defuddle cleaner to extract article-like HTTPS pages as Markdown. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion.
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.