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 TweekFawkes/prompts --skill handoffgit clone --depth 1 https://github.com/TweekFawkes/promptsWrote 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/tweekfawkes/prompts/handoff)<a href="https://agentmods.dev/skills/tweekfawkes/prompts/handoff"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/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/tweekfawkes/prompts/handoff"><img src="https://agentmods.dev/badge/skills/tweekfawkes/prompts/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.00072 | $0.00695 |
| Opus 5 | $0.00036 | $0.00347 |
| Sonnet 5 | $0.00014 | $0.00139 |
| Haiku 4.5 | $0.00007 | $0.00069 |
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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/handoff — Write a session handoff document
Write a handoff document summarising the current conversation so a fresh agent can continue the work.
Ground the handoff in real repo state
Do not invent status. Before writing, collect the facts (run only what's relevant):
git status --shortandgit --no-pager log --oneline -10— uncommitted changes and recent commits (use the real hashes).git status -sb— current branch and whether it's ahead of / behind its remote (i.e. whether commits are pushed).ls z_tickets/open/(ignore.gitkeep/ dotfiles) — backlog tickets still open.- Note any background tasks, deploys, or test runs from this session still in flight or left broken.
Use what you actually did this session as the spine, cross-checked against the state above so the doc matches reality. Be honest: if something failed, was skipped, or is uncertain, say so plainly.
Save location
Save to the z_handoff directory (create it if it doesn't exist) with a file name of YYYYMMDDHHMMSS-some_desc.md. Get the timestamp from the date +%Y%m%d%H%M%S command — do not guess it. some_desc is a short kebab-case slug of the session's focus.
Contents
Use Markdown, bullets over prose, skimmable. Cover:
- Session summary — 2-3 sentences on the focus.
- Completed work — finished tasks with concrete file paths and real commit hashes; note whether each is pushed.
- Pending work — prioritized checklist, including open
z_tickets/open/tickets and any uncommitted working-tree changes. - Key decisions — choices made and why, especially anything touching the architecture invariants in
CLAUDE.md. - Next steps — concrete, ordered actions for the next person.
- Gotchas / warnings — half-applied changes, stashes, flaky steps, env/deploy caveats, working-tree files intentionally left untouched.
- Suggested skills — which skills the next agent should invoke and when, drawn from your skill set, e.g.:
dowork(run an open ticket end-to-end),newticket(draft a new backlog ticket),openpr(push the branch and open a PR),gohome(commit a worktree back to main and clean up).
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 · 43 lines · 72 tokens per session scan A 0f6ff561f33e
handoff is a skill published in the GitHub repository TweekFawkes/prompts (2 stars, last pushed 1mo ago), licensed Unlicense. It adds 72 tokens to every session and 695 once invoked, about $0.0004 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.