Borrowing it
Nothing to install: this file belongs to aspenkit/aspens. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aspenkit/aspens/main/.claude/commands/save-handoff.mdgit clone --depth 1 https://github.com/aspenkit/aspensWrote 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.
[](https://agentmods.dev/commands/aspenkit/aspens/save-handoff)<a href="https://agentmods.dev/commands/aspenkit/aspens/save-handoff"><img src="https://agentmods.dev/badge/commands/aspenkit/aspens/save-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.
<a href="https://agentmods.dev/commands/aspenkit/aspens/save-handoff"><img src="https://agentmods.dev/badge/commands/aspenkit/aspens/save-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00010 | $0.00259 |
| Opus 5.5 | $0.00004 | $0.00104 |
| Sonnet 5.5 | $0.00002 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
save-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.
What it actually says
Write a structured handoff file to .aspens/sessions/ so a future Claude session can continue this work.
Steps
- Generate a timestamp:
YYYY-MM-DDTHH-MM-SS(replace:and.with-). - Write a markdown file to
.aspens/sessions/<timestamp>-claude-handoff.mdwith this structure:
# Claude save-tokens handoff
- Saved: <ISO timestamp>
- Reason: user-requested
- Working directory: <cwd>
## Task summary
<1-3 sentences: what you were working on and why>
## Current state
<What's done, what's in progress, what's blocked>
## Files touched
<List of files created, modified, or deleted in this session>
## Risks and open questions
<Anything the next session should watch out for>
## Next steps
<Concrete next actions to continue this work>
- Update
.aspens/sessions/index.jsonwith{ "latest": "<relative path>", "savedAt": "<ISO>", "reason": "user-requested" }. - Confirm the handoff was saved and print the file path.
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.
- 1mo ago First seen · 42 lines · 10 tokens per session scan A c114186d8988
save-handoff is a command published in the GitHub repository aspenkit/aspens (103 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 259 once invoked, about $0.0000 per session on Opus 5.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-30.
Other commands, from other repositories
init
Initialize Canonical-Driven Development in a project.
brief
Load current spec intent and lifecycle before creating a new specification.
tree-ring-certify
Generate Tree Ring harness or recall-quality evidence without confusing it with the full framework release suite.
tree-ring-recall
Recall durable Tree Ring Memory context before starting or resuming work.
tree-ring-update
Check for or install a verified Tree Ring Memory CLI update without changing installation scope.
tree-ring-status
Check receipt-backed Tree Ring harness readiness without claiming configuration is activation.