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 0xmariowu/builders-dont-cry --skill handoffgit clone --depth 1 https://github.com/0xmariowu/builders-dont-cryWrote 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/0xmariowu/builders-dont-cry/handoff)<a href="https://agentmods.dev/skills/0xmariowu/builders-dont-cry/handoff"><img src="https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/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/0xmariowu/builders-dont-cry/handoff"><img src="https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/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.00138 | $0.03174 |
| Opus 5 | $0.00069 | $0.01587 |
| Sonnet 5 | $0.00028 | $0.00635 |
| Haiku 4.5 | $0.00014 | $0.00317 |
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 10d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/handoff — Session handoff skill
Contract
One invocation produces:
- HANDOFF file — single per-topic task card at
${BDC_HOME:-$HOME/.bdc}/handoff/<topic-slug>.md, per § 1.4.2 of the canonical standard. Every file MUST carrykind: handoffin its frontmatter — this is the identity stamp/pickupuses to identify handoff files. - Verbal report (4 lines, printed to chat) — what builder copy-pastes into the next session
Canonical specs (do not duplicate here):
- HANDOFF schema →
${BDC_HOME:-$HOME/.bdc}/standards/ai-friendly-artifacts.md§ 1.4.2 - AI-friendly artifact shape →
${BDC_HOME:-$HOME/.bdc}/standards/ai-friendly-artifacts.md
Why one schema, not two: the previous design had a Schema A (<project>/HANDOFF.md, multi-branch index) alongside Schema B (this one). Schema A's per-branch sections required parsing markdown bodies (## {branch} headers, **Topic**: fields, fallback bullets) — fragile against any project that hand-wrote a HANDOFF.md with free-form ## sub-sections, which leaked into /pickup as ghost rows. The fix is to make identity explicit at write-time (kind: handoff stamp in frontmatter) and let /pickup trust the stamp instead of guessing structure.
This skill is the executor. To change format rules, edit the canonical doc, not this skill.
Phase 1 — Pick the topic file
Every session that touched code/config writes to one file: ${BDC_HOME:-$HOME/.bdc}/handoff/<topic-slug>.md.
- Same topic, same file. Before writing, scan
${BDC_HOME:-$HOME/.bdc}/handoff/*.mdfor an existing topic match (frontmattertitleor filename slug). If found → update in place. If not → create a new file${BDC_HOME:-$HOME/.bdc}/handoff/<topic-slug>.md(slug only, no date prefix; date lives in frontmatter). - The slug should be a stable kebab-case identifier (e.g.
launch-traffic-fix,pickup-display-bugs). Pick something that survives across sessions even if the headline phrasing changes. - Skip the handoff entirely for pure Q&A sessions with no code/config changes.
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.
- 10d ago First seen · 157 lines · 138 tokens per session scan A 2f95fdf04bcf
handoff is a skill published in the GitHub repository 0xmariowu/builders-dont-cry (4 stars, last pushed 4mo ago), licensed MIT. It adds 138 tokens to every session and 3,174 once invoked, about $0.0007 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.