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.
npx agentmods add commands/cloudnative-co/claude-code-starter-kit/handovergit clone --depth 1 https://github.com/cloudnative-co/claude-code-starter-kitWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00476 |
| Opus 5 | $0.00000 | $0.00238 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
handover 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/handover - Structured Session Handover
Generate a structured handover document for seamless session continuation.
Instructions
Create a handover document that captures the complete state of the current work session. This enables a fresh Claude Code session (or a different developer) to continue exactly where you left off.
Generate HANDOVER.md
Create HANDOVER.md in the project root with the following structure:
# Session Handover
## Generated: [ISO 8601 timestamp]
## Current State
- **Branch**: [current git branch]
- **Last Commit**: [hash + message]
- **Uncommitted Changes**: [list of modified/added files]
## What Was Done
[Numbered list of completed actions in this session]
## What Remains
[Checklist of remaining tasks, in order of priority]
- [ ] Task 1
- [ ] Task 2
## Key Decisions Made
[Important decisions and their rationale]
## Known Issues / Blockers
[Any issues discovered but not resolved]
## Context Files
[List of files that the next session should read first]
- path/to/critical-file-1
- path/to/critical-file-2
## Recommended Next Steps
1. Start a fresh session: `claude`
2. Read this handover: "Read HANDOVER.md and continue from where the previous session left off"
3. [Specific first action]
Rules
- Include actual git state (branch, last commit, uncommitted changes)
- Be specific about what was completed vs what remains
- List files in order of importance for context loading
- After generating, suggest running
/compactor starting a new session - The handover document should be self-contained - readable without any prior context
Session Naming Convention
After creating the handover document, suggest renaming the session for easy retrieval:
/rename [feature-name: current-status]
Naming patterns:
[auth-refactor: plan-approved]-- feature + status[bug-123: investigating]-- issue number + phase[sprint-12: day-3-reviews]-- sprint + day
This enables targeted /resume later:
claude --resume # shows recent sessions with names
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.
- 2d ago First seen · 72 lines · 0 tokens per session scan A 30c3377682dc
handover is a command published in the GitHub repository cloudnative-co/claude-code-starter-kit (147 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 476 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.