handoff

handoff is a command for Claude Code from intellegix/intellegix-code-agent-toolkit. It costs 0 tokens per session (960 once invoked), scanned A, original, MIT.

A command that records the current coding session in a handoff document, including changed files, completed work, issues, decisions, and test status.

In plain words
What is it for?
Use it at the end of a work session to document repository changes, progress, blockers, decisions, and test results in a dated Markdown file.
Why use it?
It prevents important context from being lost when work moves to another developer or agent. It also gives the next session a clear picture of what remains.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code.

Good fit Use it at the end of a work session to document repository changes, progress, blockers, decisions, and test results in a dated Markdown file.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/intellegix/intellegix-code-agent-toolkit/handoff
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.

Clone the repo
git clone --depth 1 https://github.com/intellegix/intellegix-code-agent-toolkit

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/intellegix/intellegix-code-agent-toolkit/handoff/github.svg)](https://agentmods.dev/commands/intellegix/intellegix-code-agent-toolkit/handoff)
Your own site
<a href="https://agentmods.dev/commands/intellegix/intellegix-code-agent-toolkit/handoff"><img src="https://agentmods.dev/badge/commands/intellegix/intellegix-code-agent-toolkit/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.

agentmods 80×15 button for handoff

Your own site · 80×15
<a href="https://agentmods.dev/commands/intellegix/intellegix-code-agent-toolkit/handoff"><img src="https://agentmods.dev/badge/commands/intellegix/intellegix-code-agent-toolkit/handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 960 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.00000 $0.00960
Opus 5.5 $0.00000 $0.00384
Sonnet 5.5 $0.00000 $0.00192
Haiku 4.5 $0.00000 $0.00096

Measured 1mo ago against content hash 995cf8eb76c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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.

commands/handoff.md · 160 lines

How it starts

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

Agent Handoff

Create a comprehensive handoff document for the current work session.

Task Context: $ARGUMENTS

Handoff Process

Step 1: Gather Session Information

  1. Identify all files modified in this session
  2. Summarize work completed
  3. Note any blockers or issues encountered
  4. List decisions made and their rationale

Step 2: Document Current State

  1. Run relevant status commands:

    git status
    git diff --stat
    git log --oneline -5
    
  2. Check test status:

    npm test -- --passWithNoTests 2>/dev/null || pytest --co -q 2>/dev/null || echo "No test runner detected"
    

Step 3: Create Handoff Document

Generate file at: .claude/handoffs/[YYYY-MM-DD]-[HH-MM]-[task-slug].md

Handoff Document Template

# Agent Handoff: [Task Name]

**Generated**: [Current Timestamp]
**Session Duration**: [Approximate time spent]
**Agent**: Claude Code

---

## Current Status

| Metric | Value |
|--------|-------|
| Overall Progress | X% complete |
| Phase | Planning / Implementation / Testing / Review |
| Blocked | Yes/No |
| Tests Passing | Yes/No/Partial |

## Work Completed This Session

### Tasks Finished
- [x] [Completed task 1]
- [x] [Completed task 2]

### Partial Progress
- [ ] [In-progress task] - [Current state, what's left]

## Files Modified

| File | Change Type | Description |
|------|-------------|-------------|
| `src/path/file.ts` | Created | New component for X |
| `src/path/other.ts` | Modified | Added Y method |
| `tests/path/test.ts` | Created | Tests for X |

## Key Decisions Made

### Decision 1: [Title]
- **Context**: [Why this decision was needed]
- **Choice**: [What was decided]
- **Rationale**: [Why this approach]
- **Alternatives Rejected**: [What else was considered]

## What Worked Well
- [Successful approach 1]
- [Successful approach 2]

## What Didn't Work
- **Attempted**: [Approach that failed]
- **Problem**: [Why it didn't work]
- **Resolution**: [What was done instead]

## Blockers & Dependencies

### Active Blockers
- **Blocker**: [Description]
  - **Impact**: [What it's blocking]
  - **Needed**: [What's needed to unblock]
  - **Owner**: [Who can resolve this]

### External Dependencies
- [Dependency on external team/service]

## Context for Next Agent

### Current State of Codebase
[Brief description of relevant code state - what's implemented, what's scaffolded, what's missing]

### Important Files to Review First
1. `path/to/file1.ts` - [Why it's important]
2. `path/to/file2.ts` - [Why it's important]

### Environment Setup
```bash

Read the full file on GitHub · 160 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. 1mo ago First seen · 160 lines · 0 tokens per session scan A 995cf8eb76c7

Subscribe to this mod's changes

handoff is a command published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 960 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-30.