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 Avijit07x/claude-db --skill handoffgit clone --depth 1 https://github.com/Avijit07x/claude-dbWrote 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/avijit07x/claude-db/handoff)<a href="https://agentmods.dev/skills/avijit07x/claude-db/handoff"><img src="https://agentmods.dev/badge/skills/avijit07x/claude-db/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/avijit07x/claude-db/handoff"><img src="https://agentmods.dev/badge/skills/avijit07x/claude-db/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.00087 | $0.00920 |
| Opus 5.5 | $0.00035 | $0.00368 |
| Sonnet 5.5 | $0.00017 | $0.00184 |
| Haiku 4.5 | $0.00009 | $0.00092 |
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 8d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write a handoff note
1. Gather the facts
Run this from the project root to see what memory and git already know:
claude-db catchup
Combine that with what happened in this chat. The chat is the best source for what was done and what is
still open. The output fills gaps and checks dates. If it shows a Last handoff, that is the note you
will carry forward in step 2.
2. Write the note
The first line is the title and has today's date. Get it with date '+%b %-d'. Then write at most 8 lines,
each under about 200 characters. The next chat reads this note at its start, so every line costs context.
Handoff, Oct 7:
- Done: timers, queue, mail family.
- Open: PR #18 not merged.
- Next: ask which retries to change on the worker queue.
- Decided: retries stay at 3, because the queue already backs off.
- Rejected: a second worker pool, because it doubled the mail cost.
- Watch out: tests read dist/, so run the build first.
- State: branch v0.12, 4 files uncommitted, last commit 1db3638.
Lines:
Done,OpenandNextare always there. One line each.Decided,Rejected,Watch outandStateonly when there is something real to say. Never pad.RejectedandDecidedgive the reason after "because". A rejected idea with no reason is not worth a line.Statecomes from thecatchupoutput, not from memory: theBranchline and the newest of theRecent commits. Add a pull request number only if this chat mentioned one.DecidedandRejectedstart fromDecisions and dead endsin the output, plus this chat.- Name real things: a file, a pull request number, a command, a decision. Do not write
various changes. - Use only what this chat or the output showed. Mark anything you are unsure of with
(guess). - If there is no clear next step, write
- Next: no clear next step yet.Do not invent one. - Leave out secrets, tokens, passwords and personal data.
Carry forward. Keep a line from the previous handoff when it is still true and still matters, and add the
date to it, for example (Oct 5). Drop what is finished or wrong. If the note is over 8 lines, shorten lines
or drop the oldest finished ones. Never drop a Rejected line that is still true.
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.
- 8d ago First seen · 79 lines · 87 tokens per session scan A cb43eb815f36
handoff is a skill published in the GitHub repository Avijit07x/claude-db (234 stars, last pushed 5d ago), licensed Apache-2.0. It adds 87 tokens to every session and 920 once invoked, about $0.0003 per session on Opus 5.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-10-08.
Other skills, from other repositories
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
resume
Load a previous session from TokenMizer graph memory. Returns a compact context block (100-600 tokens) covering goals, completed work, decisions, open tasks, and files. Inject this as system context to continue exactly where you left off. Use when user says "resume", "continue from last time", "load my project", "what…
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
setup-repo-skills
Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.