stack-handoff

A project handoff record that saves the current task, decisions, unfinished work, and Git state for later.

In plain words
What is it for?
Use it to write a handoff file before stopping work and read the latest handoff when continuing an existing task.
Why use it?
It prevents important context from being lost when a session ends, a teammate takes over, or work resumes after a break.

Skill for Claude CodeCodex

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/drmahdikazempour/agent-stack/stack-handoff
Any agent
npx skills add drmahdikazempour/agent-stack --skill stack-handoff
Clone the repo
git clone --depth 1 https://github.com/drmahdikazempour/agent-stack

Made for: Claude Code, Codex.

Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 249 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.00078 $0.00249
Opus 5 $0.00039 $0.00125
Sonnet 5 $0.00016 $0.00050
Haiku 4.5 $0.00008 $0.00025

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

Security

Grade A, and why

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

skills/stack-handoff/SKILL.md · 24 lines

What it actually says

stack-handoff

Persist and resume working state across sessions.

Write a handoff

npx @drmahdikazempour/agent-stack handoff write captures into .agent-stack/handoff.md:

  • current git branch, uncommitted changes, recent commits,
  • a template for the current task, decisions made, and next steps.

Edit the generated file to fill in the narrative parts before you stop.

Resume

npx @drmahdikazempour/agent-stack handoff resume prints the latest handoff so you can continue exactly where the last session stopped.

When to use

  • At the end of any working session.
  • Before switching branches or context.
  • At the start of any resumed or handed-off task — resume first, then continue.
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 · 24 lines · 78 tokens per session scan A a0ab793c3adf

Subscribe to this mod's changes

stack-handoff is a skill published in the GitHub repository drmahdikazempour/agent-stack (2 stars, last pushed 3mo ago), licensed MIT. It adds 78 tokens to every session and 249 once invoked, about $0.0004 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.