handoff-session

handoff-session is a skill for Claude Code, Codex from SNIKO/agent-skills. It costs 29 tokens per session (861 once invoked), scanned A, original, MIT.

A format for summarizing a work session so another coding agent can continue it. It records where the work began, decisions and changes, important files, and any running processes or uncertainties.

In plain words
What is it for?
Use it when ending, compacting, or handing off a session involving code changes, plans, files, decisions, or processes that another agent must continue.
Why use it?
It prevents the next agent from having to reconstruct the session from scratch. It preserves exact paths and the practical context needed to resume work safely.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when ending, compacting, or handing off a session involving code changes, plans, files, decisions, or processes that another agent must continue.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sniko/agent-skills/handoff-session
Install

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.

Any agent
npx skills add SNIKO/agent-skills --skill handoff-session
Clone the repo
git clone --depth 1 https://github.com/SNIKO/agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for handoff-session

README.md
[![agentmods](https://agentmods.dev/badge/skills/sniko/agent-skills/handoff-session.svg)](https://agentmods.dev/skills/sniko/agent-skills/handoff-session)
Your own site
<a href="https://agentmods.dev/skills/sniko/agent-skills/handoff-session"><img src="https://agentmods.dev/badge/skills/sniko/agent-skills/handoff-session.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 861 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.00861
Opus 5 $0.00015 $0.00430
Sonnet 5 $0.00006 $0.00172
Haiku 4.5 $0.00003 $0.00086

Measured 7d ago against content hash 119894a191fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

handoff-session 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 7d 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.

skills/handoff-session/SKILL.md · 91 lines

What it actually says

<decision_rules>

  • Prefer precise session facts over general project descriptions.
  • Include only items touched, created, decided, started, or made relevant in this session.
  • If a required section has no information, write none; never omit required sections.
  • Use absolute paths for files, directories, worktrees, plans, and memory artifacts when a path is known. If only a relative path is known, resolve it against the current working directory before writing it.
  • If a plan or task list drove the session, list it first under Key files for next session.
  • For running state, include how the next agent can stop or resume the process when that information is known.
  • If evidence is uncertain or unavailable, say so briefly instead of inventing state. </decision_rules>

<output_format> Use exactly this structure every time:

# Session Handoff — <one-line title of what this session was about>

## Where it started
<2-3 sentences: what the user asked for, key framing or constraints that emerged>

## Decisions locked + what shipped
- <decision or change> — <why it matters, and where it lives if applicable>
- ...

## Key files for next session
- `<absolute path>` — <why the next agent should read this first>
- Plan file: `<absolute path>` — <if a plan drove the session, otherwise `none`>
- Notes or memory touched: `<absolute path>` — <if any, otherwise `none`>

## Key facts for next session
- <fact> — <why it matters>
- ...

## Deferred + open questions
- Deferred: <item> — <why pushed to later>
- Open: <question needing user input> — <context>

## Pick up here
<leave empty, will be filled by the user>

</output_format>

<completion_criteria> Before sending, verify that:

  • Every required section is present.
  • No section contains invented or assumed state.
  • All known file paths are absolute.
  • Running processes, ports, worktrees, and branches are explicit or marked none.
  • Verification commands are specific and tied to expected or observed outcomes.
  • Pick up here contains one focused next action. </completion_criteria>
Changes

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.

  1. 7d ago First seen · 91 lines · 29 tokens per session scan A 119894a191fa

Subscribe to this mod's changes

handoff-session is a skill published in the GitHub repository SNIKO/agent-skills (2 stars, last pushed 15d ago), licensed MIT. It adds 29 tokens to every session and 861 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

html-artifacts

Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.

langchain-ai/open-swe · 51 tokens

bootstrap-repo-analysis

First-time analysis of a repository with no prior reviewer outcomes. Crawl historical merged-PR review feedback with the gh CLI (plus any preloaded samples), extract the team's review norms, and synthesize the initial per-repo review-style prompt. Use this for a cold-start repo; use continual-learning instead once the…

langchain-ai/open-swe · 73 tokens

baby-sit

Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.

langchain-ai/open-swe · 30 tokens

continual-learning

Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…

langchain-ai/open-swe · 89 tokens

oracle

Oracle second-model review: bundle prompts/files, debug, refactor, design.

steipete/oracle · 18 tokens

latent-potential

First-principles, team-of-experts assessment of a software project that surfaces latent potential; underexploited assets, a sharper north star, missing high-leverage capabilities, better framing and messaging. Produces a prioritized, evidence-grounded report with cheap probes, a reframe candidate, a stop-doing list…

petekp/claude-code-setup · 191 tokens