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/romiluz13/auto-pi/session-handoffnpx skills add romiluz13/auto-pi --skill session-handoffgit clone --depth 1 https://github.com/romiluz13/auto-piWhat 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.00083 | $0.00906 |
| Opus 5 | $0.00042 | $0.00453 |
| Sonnet 5 | $0.00017 | $0.00181 |
| Haiku 4.5 | $0.00008 | $0.00091 |
Grade A, and why
session-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 3d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff
Transfer work from one Pi session to another without losing context. This is the cross-session version of compact-safe — instead of compressing the current session, you're moving the work to a new session.
When to use
- Session is getting long (approaching compaction) and you want a fresh context
- You need to continue work in a different project or branch
- You're transferring work to a specialist session (e.g., handing a plan to a builder)
- The user says "handoff", "continue in a new session", "pass this to X"
Procedure
-
Write the handoff doc. The
handoffextension (extensions/handoff.ts) writes a deterministicHANDOFF.mdfrom recent turns + the last compaction summary. No LLM call — it's a snapshot. If the extension is available, it fires automatically. If not, write a markdown file todocs/handoff/<YYYY-MM-DD>-session-handoff.mdwith:- Active constraints — what must not change, what rules are in effect
- Current state — what's done, what's in progress, what's blocked
- Key decisions — what was decided and why
- Errors (verbatim) — any error messages, stack traces, or failures
- Next steps — what the receiving session should do first
-
Save key decisions to memory. Use the
memorytool to save:- Architecture decisions (to
projectormemorytarget) - Failures and corrections (to
failuretarget with category) - User preferences discovered during the session (to
usertarget)
Capture memory payload BEFORE validation — compaction can fire between return and parse. If memory is full, save to the handoff doc instead.
- Architecture decisions (to
-
Discover the target session. Run
intercom({ action: "list" })to see active sessions. Filter by:- Same cwd (sessions in the same project)
- Session name (if the user named it with
/name) - Status (look for "idle" or "active" sessions that can receive work)
-
Notify the target session. Run
intercom({ action: "send", to: "<session-id-or-name>", message: "..." })with:- The handoff doc path
- A 3-line summary of what to do next
- Any blocking constraints ("don't touch X", "Y is in progress")
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.
- 3d ago First seen · 63 lines · 83 tokens per session scan A 48d5fc34e809
session-handoff is a skill published in the GitHub repository romiluz13/auto-pi (11 stars, last pushed 17d ago), licensed MIT. It adds 83 tokens to every session and 906 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-30.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
teach
Teach the user a new skill or concept, within this workspace.
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.