handoff-management

handoff-management is a skill for Claude Code from aaronb305/claude-cortex. It costs 39 tokens per session (823 once invoked), scanned A, original, MIT.

A session handoff tool that records unfinished work, completed tasks, pending tasks, blockers, and useful context in markdown files.

In plain words
What is it for?
Use it to save progress, view the latest handoff, or list earlier handoffs before continuing work.
Why use it?
It prevents important details from being lost when a coding session ends, changes tasks, or runs out of context.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the claude-cortex plugin — 3 skills, 7 agents, 1 MCP server shipped together

Good fit Use it to save progress, view the latest handoff, or list earlier…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aaronb305/claude-cortex/handoff-management
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 aaronb305/claude-cortex --skill handoff-management
Clone the repo
git clone --depth 1 https://github.com/aaronb305/claude-cortex

Made for: Claude Code.

Or install claude-cortex, the plugin that ships this one along with the rest of its 3 skills, 7 agents, 1 MCP server.

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-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/aaronb305/claude-cortex/handoff-management.svg)](https://agentmods.dev/skills/aaronb305/claude-cortex/handoff-management)
Your own site
<a href="https://agentmods.dev/skills/aaronb305/claude-cortex/handoff-management"><img src="https://agentmods.dev/badge/skills/aaronb305/claude-cortex/handoff-management.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 823 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.00039 $0.00823
Opus 5 $0.00019 $0.00411
Sonnet 5 $0.00008 $0.00165
Haiku 4.5 $0.00004 $0.00082

Measured 6d ago against content hash 6786975b9ca1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

handoff-management 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 6d 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-management/SKILL.md · 140 lines

How it starts

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

Handoff Management Skill

Handoffs capture work-in-progress state, enabling seamless session continuity. Unlike learnings (permanent knowledge), handoffs capture ephemeral state: what's done, what's pending, and what's blocking progress.

When to Use Handoffs

Save Progress

  • Before ending a session with incomplete work
  • Before context compaction (automatic via PreCompact hook)
  • When switching between tasks

Resume Work

  • Starting a new session on existing work
  • After context was cleared or compacted
  • Picking up where you left off

Handoff Commands

Create a Handoff

# Basic handoff
uv run cclaude handoff create

# With specific tasks
uv run cclaude handoff create \
  --completed "Implemented auth middleware" \
  --completed "Added JWT validation" \
  --pending "Write integration tests" \
  --pending "Add password reset flow" \
  --blocker "Need API credentials for OAuth" \
  --context "Using RS256 for token signing"

View Latest Handoff

uv run cclaude handoff show

List All Handoffs

uv run cclaude handoff list

Handoff Format

Handoffs are stored as markdown with YAML frontmatter:

---
session_id: abc-123
timestamp: 2025-12-27T14:30:00+00:00
---

## Completed
- Implemented auth middleware
- Added JWT validation

## Pending
- Write integration tests
- Add password reset flow

## Modified Files
- src/auth/middleware.py
- src/auth/jwt.py

## Blockers
- Need API credentials for OAuth

## Context
Using RS256 for token signing. The auth service expects tokens
in the Authorization header, not cookies.

Storage Location

project/.claude/handoffs/
└── <session_id>/
    └── handoff-<timestamp>.md

Best Practices

When Creating Handoffs

  1. Be specific about pending tasks

    • Bad: "Finish auth"
    • Good: "Write integration tests for JWT refresh flow"
  2. Document blockers clearly

    • What's blocking?
    • What's needed to unblock?
    • Who can help?
  3. Include relevant context

    • Key decisions made
    • Important file paths
    • Configuration details

Read the full file on GitHub · 140 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. 6d ago First seen · 140 lines · 39 tokens per session scan A 6786975b9ca1

Subscribe to this mod's changes

handoff-management is a skill published in the GitHub repository aaronb305/claude-cortex (2 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 823 once invoked, about $0.0002 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

media-ingest

Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.

garrytan/gbrain · 52 tokens

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

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.

opensquilla/opensquilla · 44 tokens

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…

shiwenwen/hope-agent · 115 tokens

establishing-project-context

Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.

GanyuanRan/Aegis · 45 tokens