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 pop-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/pop-handoff)<a href="https://agentmods.dev/skills/aiya000/dotfiles/pop-handoff"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/pop-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/pop-handoff"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/pop-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.00077 | $0.00658 |
| Opus 5.5 | $0.00031 | $0.00263 |
| Sonnet 5.5 | $0.00015 | $0.00132 |
| Haiku 4.5 | $0.00008 | $0.00066 |
Grade A, and why
pop-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 10d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pop-handoff
read-handoff is git stash apply: it reads the handoff and leaves it. This is git stash pop:
the same reading, and then the handoff is gone -- from the repository, so neither the local
machine nor a cloud session finds it again.
Handoffs are perishable. Once a session has picked one up, the next session should find the handoff that session writes, not this one again.
Steps
- Run the
read-handoffskill, with this skill's argument if one was given, and do all of it: the issue overview, finding the handoff, following it to the memory file. Note which handoff file it picked up - Remove that handoff, and only that one:
- In
~/.ai-memory/handoff/: with thesync-memoryskill,drop 'handoff: pop <file>' handoff/<file>.md handoff/<file>.declined. It is removed and pushed, with itsdecline-handoff-suggestionmarker if it had one; the repository's history keeps it, so it can be brought back - In an old local place (
~/tmp/claude-handoff/,${TMPDIR:-/tmp}/claude-handoff/): not in the repository, sorm-dust <path>and its.declinedmarker, if any (rmin a cloud session, where there is norm-dust)
- In
- Run the
sync-memoryskill (sync) -- always, on your own, never left to the user. It pushes the removal if thedropcould not - Say in one line which file was removed, and whether the removal was pushed. Then carry on with what the handoff says to do first -- the pop is not the end of the job
When not to remove it
read-handofffell back to another project's handoff (none for this one). AskUserQuestion first -- "Remove it" / "Leave it" -- since it was written for a different session- The handoff could not be followed -- the memory file it names is missing, or the user stopped partway. Leave it and say why, so it can be popped once it has actually been picked up
- The memory file the handoff points at is never removed. It is the durable half, and other sessions still read it
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.
- 10d ago Changed · +2 lines 5cd3591888a3
- 17d ago Changed e9bbc82aa531
- 20d ago First seen · 40 lines · 77 tokens per session scan A d1d399073efd
pop-handoff is a skill published in the GitHub repository aiya000/dotfiles (21 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 658 once invoked, about $0.0003 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-26.
Other skills, from other repositories
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.
monitor__ci_status
An automated monitor for GitHub Actions, the service that runs checks such as tests after code changes. It watches all checks after a pull request or a push to a pull-request branch and can invoke a failure-recovery process.
monitor__pull_request_conflict
An automated check for GitHub pull requests, which are proposed code changes awaiting review or merging.