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 skills add aiya000/dotfiles --skill create-handoffgit clone --depth 1 https://github.com/aiya000/dotfilesWrote 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/skills/aiya000/dotfiles/create-handoff)<a href="https://agentmods.dev/skills/aiya000/dotfiles/create-handoff"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/create-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/skills/aiya000/dotfiles/create-handoff"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/create-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.00134 | $0.02597 |
| Opus 5.5 | $0.00054 | $0.01039 |
| Sonnet 5.5 | $0.00027 | $0.00519 |
| Haiku 4.5 | $0.00013 | $0.00260 |
Grade A, and why
create-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 18d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
create-handoff
Writes the handoff prompt for the next session, and puts it where read-handoff will find it on
its own. The point of the pair is that no one has to carry a path between sessions.
First: save the memory, then write the handoff around it
Run the save-memory skill before writing the handoff, unless the user said not to
(/create-handoff --no-memory, 「メモリーは要らない」, and the like). The two files split the
session between them, and each fact is written once, in the file it belongs to:
- The memory file (
~/.ai-memory/YYYY-MM-DD-{project}-{topic}.md) carries the durable half -- decisions with their reasons, the gotchas that cost time, the user's preferences, what is still open. Dense English, read by any later session, still worth having in a month - The handoff file carries the perishable half -- where the branch stands right now, what to do first, who is waiting on what, how the user is doing. Written for the very next session, and stale within days
Never copy the memory's content into the handoff. The handoff names the memory file and tells the next session to read it; that is the whole of the overlap between them.
Note the path save-memory wrote to -- the handoff's first section needs it.
If save-memory was skipped, say so in that section, and then this handoff carries everything
itself, as it used to.
Where the file goes
~/.ai-memory/handoff/, in the same git repository as the memory files. It is shared by the
local machine and Claude Code cloud sessions, so a handoff written on one side is picked up on the
other -- but only once it is pushed (see After writing).
- Get the repository ready with the
sync-memoryskill (prepare). Ifsave-memoryjust ran, it already did this; running it again only pulls mkdir -p ~/.ai-memory/handoff
The path is deterministic on purpose. A mktemp -d path cannot be found again by the next
session, which is the whole thing this pair exists to avoid.
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.
- 18d ago Changed · +6 lines ef90d4efdfeb
- 25d ago Changed bf09a026ace5
- 28d ago Changed · +12 lines · +17 tokens per session 707100816db4
- 1mo ago Changed · +30 lines · +23 tokens per session b7de155064f1
- 1mo ago Changed · +36 lines · +21 tokens per session 6768b7530659
- 1mo ago First seen · 82 lines · 73 tokens per session scan A 112997cd5377
create-handoff is a skill published in the GitHub repository aiya000/dotfiles (21 stars, last pushed 10d ago), licensed MIT. It adds 134 tokens to every session and 2,597 once invoked, about $0.0005 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-09-07.
Other skills, from other repositories
rex
Use the rex CLI to manage Rex sessions, open tabs, arrange panes, run commands, inspect terminal output, and control connected Rex apps.
use-notion
Reference for using the Notion API via the notion-agent subagent. Use to expore and update Notion workspace content.
restart__pull_request
A pull-request restart workflow for replacing a messy review with a new pull request containing one clean commit and a summary of the earlier discussion.
rescue__pull_request_review
An automated workflow for handling GitHub pull-request review comments, applying requested code changes, committing them, and pushing them back.
submit__pull_request
An automated pull-request submission workflow. A pull request is a request for a code change to be reviewed and merged; this workflow writes its explanation, creates it, watches its automated checks, and fixes failed checks.
write__pull_request
A workflow for writing a pull request description, the explanation attached to a proposed code change for review. It analyses the changes and commit history.