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 upex-galaxy/agentic-qa-boilerplate --skill session-handoffgit clone --depth 1 https://github.com/upex-galaxy/agentic-qa-boilerplateWrote 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/upex-galaxy/agentic-qa-boilerplate/session-handoff)<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/session-handoff"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/session-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/upex-galaxy/agentic-qa-boilerplate/session-handoff"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/session-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.00225 | $0.02193 |
| Opus 5.5 | $0.00090 | $0.00877 |
| Sonnet 5.5 | $0.00045 | $0.00439 |
| Haiku 4.5 | $0.00022 | $0.00219 |
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 5d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff
A handoff is context transplanted, not context summarized. The successor is not a reader being briefed on someone else's work; it IS this session, with a new window. Everything it needs to act must be on disk, addressable, and true when it reads.
The skill is small on purpose. The heavy artifact is the markdown it produces, and the whole contract lives in .agents/skills/session-handoff/references/capture-contract.md.
What this is not
| Looks similar | Actually is | Use |
|---|---|---|
| hand a scoped task to another session and supervise it | orchestration: Task, Dispatch, mailbox, the work comes back | /orca-orchestration |
| hand work away and stop caring | ownership transfer of a TASK, one direction, no return | the binary's own orca-cli guide |
| remember a decision for next month | durable cross-session fact, project-scoped | Engram (mem_save) |
| shrink the window and keep going | harness compaction, lossy, not addressable, not yours to shape | nothing to do |
| hand the whole SESSION to its own successor | this skill | here |
The distinction that matters: compaction keeps what a summarizer judged salient. A handoff keeps what the NEXT actor needs, which is a different set, and it is written by the only party that knows the difference.
When to write one
Manual is the primary trigger and that is by design. The human notices the window filling, says so, and the skill runs. No polling, no nagging, no token spent guessing.
Whether any harness can trigger this automatically is answered, with citations, in .agents/skills/session-handoff/references/auto-trigger.md. Read it before promising the owner an automatic mode.
Write one when any of these is true:
- the context window is past the owner's threshold (~500k tokens unless the owner names a different one; it is a per-owner judgement about where this model starts degrading, not project configuration, so it stays in the conversation and not in a yaml key)
- the session is about to end with work still in flight
- the session is about to do something that will itself consume a large slice of the window (a big harvest, a long file read) and the remaining budget will not cover the work after it
- the owner asks
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed · +2 lines d13a2208561b
- 12d ago Changed 845005419370
- 15d ago Changed · +1 lines · +15 tokens per session e3127d0df8a9
- 21d ago Changed c9789a908bee
- 23d ago Changed · +2 lines db9e0b10c1b4
- 28d ago First seen · 82 lines · 210 tokens per session scan A 33eea221bbb9
session-handoff is a skill published in the GitHub repository upex-galaxy/agentic-qa-boilerplate (26 stars, last pushed 4d ago), licensed MIT. It adds 225 tokens to every session and 2,193 once invoked, about $0.0009 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-09-19.
Other skills, from other repositories
ai-csv-excel-merger
A tool for combining CSV and Excel materials into one organized result while identifying conflicting fields.
ai-gws-docs
A business-diagnosis assistant for turning document-related input into a summary, conclusions, recommended actions, and reusable deliverables.
ai-gws-gmail
A business-diagnosis assistant for turning Gmail-related input into a summary, conclusions, recommended actions, and reusable deliverables.
ai-gws-sheets
A business-diagnosis assistant for turning spreadsheet-related input into a summary, conclusions, recommended actions, and reusable deliverables.
ai-meeting-to-tasks
A meeting follow-up assistant that turns meeting information into tasks, decisions, risks, and follow-up items.
cog-braindump-capture
Capture raw thoughts with automatic domain classification and vault routing.