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 read-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/read-handoff)<a href="https://agentmods.dev/skills/aiya000/dotfiles/read-handoff"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/read-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/read-handoff"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/read-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.00064 | $0.00523 |
| Opus 5 | $0.00032 | $0.00262 |
| Sonnet 5 | $0.00013 | $0.00105 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
read-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 3d 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
read-handoff
Picks up where the last session stopped. The user should not have to supply a path.
Finding the file
-
The directory, in the same order
create-handoffuses:~/tmp/claude-handoff/when~/tmpexists${TMPDIR:-/tmp}/claude-handoff/
-
Work out the project the same way it does:
common=$(git rev-parse --path-format=absolute --git-common-dir 2>/dev/null) project=$( [ -n "$common" ] && basename "$(dirname "$common")" || basename "$PWD" ) -
Take the last of
<project>-*.mdsorted by name -- the names carry the timestamp -
If there is none for this project, take the newest
*.mdin the directory and say which project it was written for before acting on it -
If there is nothing at all, say so and list what the directory does hold. Do not guess
An argument overrides all of that: a path is read directly, anything else is treated as a project name.
Then
Read the whole file and treat it as the user's instructions for this session, not as
background reading. Do what it says first -- usually reading AGENTS.md and getting the branch
level -- before touching anything else.
Two things the file cannot know:
- It was true when it was written. Check the branch, the open Issues, and anything it calls 未解決 against the world as it is now, and say so where they have moved on
- It may simply be wrong. Where the code disagrees with it, the code wins
Say in a line or two which file was picked up and what it says the first job is. Do not replay the whole thing back at the user -- they wrote 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.
- 3d ago First seen · 45 lines · 64 tokens per session scan A 6f75a4a5c8ca
read-handoff is a skill published in the GitHub repository aiya000/dotfiles (19 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 523 once invoked, about $0.0003 per session on Opus 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
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.
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.