handing-off-session

A session handoff note is a structured Markdown file that records the current work state for a later session. It captures completed work, decisions, recent Git changes, blockers, and unfinished tasks.

In plain words
What is it for?
Use it to create a handoff file at the end of a coding session or before a long break. It is also useful when another session needs to continue the same project.
Why use it?
It prevents important context from being lost when a session ends, a project changes, or the conversation becomes too long. The next session can use the note to resume work.

Skill for Claude CodeCodex

Part of the cc-meta plugin — 7 skills, 1 hook shipped together

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.

agentmods
npx agentmods add skills/qte77/claude-code-plugins/handing-off-session
Any agent
npx skills add qte77/claude-code-plugins --skill handing-off-session
Clone the repo
git clone --depth 1 https://github.com/qte77/claude-code-plugins

Made for: Claude Code, Codex.

Or install cc-meta, the plugin that ships this one along with the rest of its 7 skills, 1 hook.

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 595 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00026 $0.00595
Opus 5 $0.00013 $0.00298
Sonnet 5 $0.00005 $0.00119
Haiku 4.5 $0.00003 $0.00060

Measured 2d ago against content hash 99482399ede0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

handing-off-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 2d 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.

plugins/cc-meta/skills/handing-off-session/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Session Handoff

Target: $ARGUMENTS

Captures session state as a structured markdown note for the next session to pick up. Stateless — markdown files only, no database, no daemon.

Arguments

Position Name Required Default Description
1 output-path no auto Where to write the handoff note.

Default output path: .claude/handoffs/YYYY-MM-DD-<short-description>.md

The <short-description> is a 2-4 word slug derived from the session's primary focus (e.g. 2026-04-06-session-handoff-skill.md).

When to Use

  • End of a work session
  • Switching context to a different project or task
  • Before a long break
  • When context window is getting full and you want to preserve state

Workflow

  1. Scan conversation — Identify completed actions, decisions, and pending work from the current session context.

  2. Check git state — Run git diff --stat and git log --oneline -10 to capture recent changes and commits.

  3. Extract signals — Collect decisions made, alternatives rejected, blockers encountered, and open questions.

  4. Ensure output dir — Create .claude/handoffs/ if it doesn't exist.

  5. Write handoff note — Use the template below. Be concise — enough to resume, no more.

Output Template

# Session Handoff — <date>

## What Was Done
[Completed work, key commits, PRs created/merged]

## What's Pending
[Open tasks, unfinished work, next steps]

## Key Decisions
[Architectural choices, trade-offs made, rejected alternatives]

## Modified Files
[List of files changed with brief reason]

## Blockers
[External dependencies, open questions, things that need user input]

Picking Up a Handoff

Next session can read the latest handoff:

# Find latest handoff
ls -t .claude/handoffs/*.md | head -1

Or read all recent handoffs to rebuild context across multiple sessions.

Quality Check

  • Correct > Complete > Minimal (ACE-FCA)
  • ~20-50 lines output per handoff
  • Every item traces to a concrete action or artifact
  • No raw dumps — structured summaries only

Read the full file on GitHub · 91 lines

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. 2d ago First seen · 91 lines · 26 tokens per session scan A 99482399ede0

Subscribe to this mod's changes

handing-off-session is a skill published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 26 tokens to every session and 595 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

orchestrator

FULLY AUTONOMOUS Flutter development pipeline orchestrator. Smart routing: PM analyzes -> creates targeted tasks -> Orchestrator executes only needed agents. Supports Asana task URLs. Includes QE verification via Maestro E2E tests. 7-phase flow: PM -> TodoWrite -> Execute -> Review -> Tests -> QE E2E -> Close.

aleksandr-chaika/flutter-clean-arch-skills · 72 tokens

flutter-guide

Flutter/BLoC Clean Architecture patterns, review checklists, and testing guides. Background knowledge for flutter-dev, flutter-reviewer, flutter-tester. Not user-invocable.

aleksandr-chaika/flutter-clean-arch-skills · 39 tokens

maestro-flutter

Maestro E2E testing knowledge for Flutter apps. YAML-based flows, TestKeys, visual regression, Maestro MCP integration. Background knowledge for QE E2E testing phase.

aleksandr-chaika/flutter-clean-arch-skills · 41 tokens

android-kotlin-compose

Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…

and3r817/dot-claude-plugins · 84 tokens

android-kotlin-coroutines

Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…

and3r817/dot-claude-plugins · 87 tokens

codex-advisor

Advisory consultation skill for architectural reviews, design decisions, code analysis, and technology evaluation. Codex provides recommendations without making code changes. Invoked by phrases like "consult Codex", "get Codex's opinion", "ask Codex about", "have Codex review", "Codex analysis", "validate this…

and3r817/dot-claude-plugins · 85 tokens