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 forest/agent-skills --skill session-handoffgit clone --depth 1 https://github.com/forest/agent-skillsWrote 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/forest/agent-skills/session-handoff)<a href="https://agentmods.dev/skills/forest/agent-skills/session-handoff"><img src="https://agentmods.dev/badge/skills/forest/agent-skills/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/forest/agent-skills/session-handoff"><img src="https://agentmods.dev/badge/skills/forest/agent-skills/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.00000 | $0.00749 |
| Opus 5.5 | $0.00000 | $0.00300 |
| Sonnet 5.5 | $0.00000 | $0.00150 |
| Haiku 4.5 | $0.00000 | $0.00075 |
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 2mo 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff Skill
Generates a structured, deterministic session summary designed to be fed into a new Claude Code session or used with /compact to preserve continuity without relying on auto-compact's generative summarization.
The Problem This Solves
Auto-compact summarizes freely — it infers, fills gaps, and occasionally fabricates continuity. The result is non-deterministic and degrades session fidelity, especially for complex consulting and architecture work where rationale, constraints, and rejected options are as important as decisions made.
This skill produces a terse, fact-only summary that can be fed verbatim into a new session as a deterministic context handoff.
When to Trigger
Trigger this skill when:
- User mentions context limit, compacting, or starting a new session
Ctxpercentage is approaching 60% (the recommended threshold for consulting work)- User says "save where we are", "session summary", "handoff", or similar
- A long architecture or consulting session is wrapping up a phase
The Summary Prompt
Use this prompt verbatim when generating the handoff. Do not deviate from the structure or add sections not listed here.
Summarize this session using exactly these sections:
- Decisions made (include rationale for each decision)
- Active constraints (client-specific, technical, scope)
- Committed AWS service choices (services already selected and why)
- Rejected options (include the reason each was rejected)
- Current state of work (what is done, in-progress, not started)
- Open questions (unresolved items that must carry forward)
- Key entities (client name, system names, integrations, stakeholders)
Rules:
- Be terse. One to two sentences per item maximum.
- No inferred information. If it was not explicitly stated in this session, omit it.
- No filler, transitions, or commentary between sections.
- Omit any section that has nothing explicitly stated.
- Do not summarize the summary. Output the sections only.
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.
- 2mo ago First seen · 69 lines · 0 tokens per session scan A e3d3ab696363
session-handoff is a skill published in the GitHub repository forest/agent-skills (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 749 tokens. 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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, source notes, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
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…