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/viknesh20-20/claude-code-tool-kit/handoffnpx skills add viknesh20-20/claude-code-tool-kit --skill handoffgit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-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/viknesh20-20/claude-code-tool-kit/handoff)<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/handoff"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-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.00054 | $0.00932 |
| Opus 5 | $0.00027 | $0.00466 |
| Sonnet 5 | $0.00011 | $0.00186 |
| Haiku 4.5 | $0.00005 | $0.00093 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/handoff
Write an end-of-session handoff summary so the next session — yours, your teammate's, or a future-you's — can resume work without losing context.
When to use
- End of a working session, even a short one, if work is left unfinished.
- Before stepping away from a long-running task (deploy in progress, migration mid-flight, large refactor in progress).
- Before switching contexts to a different project.
- After a meaningful milestone (feature shipped, decision made, blocker hit).
Operating method
Read the current session transcript and produce a structured summary. Save it to .claude/memory/handoffs/<YYYY-MM-DD>.md. If a handoff already exists for today, append to it (don't overwrite — sessions can resume mid-day).
Sections to populate
---
name: handoff-<YYYY-MM-DD>-<HH-MM>
type: handoff
description: <one-line: what was the focus today?>
created: <YYYY-MM-DD HH:MM TZ>
---
# Handoff — <date>
## Focus today
<2–3 sentences. The actual goal, not the title.>
## What we did
- <specific change, with file paths or commit refs>
- <…>
## What's left for next session
- [ ] <task 1, with enough detail to start cold>
- [ ] <task 2>
## Blocked / waiting
- <blocker, who/what we're waiting on, when expected>
## Decisions made
- <decision> — chosen because <reason>. Reversible if <condition>.
## Decisions awaiting the user
- <question> — needs answer before <next step>.
## To verify before continuing
- <test that should still pass>
- <metric that should still be in budget>
- <thing the user said they'd check>
## Surprises / things I learned
- <non-obvious fact about the codebase or domain>
(if it'll matter beyond this week, also save as a project memory)
## Open files / branches
- Branch: <name>
- Uncommitted files: <list>
- Stash entries: <list>
## Next concrete action
<the single first thing to do next session — small enough to not need re-thinking>
Update the index
Append to .claude/memory/MEMORY.md:
## Handoffs
- [<YYYY-MM-DD>](memory/handoffs/<YYYY-MM-DD>.md) — <focus from description>
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 · 115 lines · 54 tokens per session scan A 4112819103f3
handoff is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 932 once invoked, about $0.0003 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
faq-mine
Mine docs/faq.md from README.md, docs/.md, and the pi-hermes memory stores. Dispatches @fast subagents per source, dedupes against the existing FAQ, and merges entries in caveman style. Use when asked to "build / regenerate / extend the FAQ", "mine docs into FAQ", "mine hermes memory into FAQ", "surface runtime…
distill-session-knowledge
Offline-mine this project's pi session JSONL logs into reusable, verified knowledge: extracts faults, decisions, corrections, procedures and docs, promotes only recurring patterns, and routes artifacts into skillmanage, memory and docs. Use on "mine my sessions", "distill session knowledge", "extract lessons from…
project-manager
Manage project-scoped knowledge bases with notes, decisions, and bookmarks. Use when the user wants to create/manage projects, add/view/search notes or decisions for a project, manage bookmarks (add, list, tag to projects), switch project context for conversation, or search across projects. Triggers on phrases like…
lore
Curating cross-agent knowledge and institutional memory: extracts patterns from agent journals into METAPATTERNS.md, detects knowledge decay, propagates best practices. Use for memory curation.
a2wave-memory
Progressively recall and maintain a2wave cross-session memory through a compact startup catalog, bounded topics, and searchable history.
optimize-learnings
Audit and curate the learnings memory namespace — the one namespace nothing re-derives, so the only one that rots. Runs moflo's mechanical audit to nominate stale, unused, and near-duplicate entries, then decides entry by entry whether to keep, retire, compress, or merge, and propagates the result to the shared…