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 apply-handoff-to-agents-mdgit 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/apply-handoff-to-agents-md)<a href="https://agentmods.dev/skills/aiya000/dotfiles/apply-handoff-to-agents-md"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/apply-handoff-to-agents-md/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/apply-handoff-to-agents-md"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/apply-handoff-to-agents-md.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.00083 | $0.02104 |
| Opus 5.5 | $0.00033 | $0.00842 |
| Sonnet 5.5 | $0.00017 | $0.00421 |
| Haiku 4.5 | $0.00008 | $0.00210 |
Grade A, and why
apply-handoff-to-agents-md 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
apply-handoff-to-agents-md
A handoff note is written to be thrown away: it tells the next session what to do next, and next week that is wrong. But a handoff is also where the session's hard-won facts get written down for the only time -- the trap that cost an hour, the reason a design went the way it did, the command that has to be run a particular way.
This skill separates the two. What is true about the repository moves into AGENTS.md, where
every future session reads it. What is true only about that moment stays in the handoff and
expires with it.
This is not apply-to-agents-md-git-root
That skill distils the current conversation, into one file at the repository root.
This one reads a handoff file, and spreads what it finds across
{repo-root}/[...children]/AGENTS.md -- root, tests/e2e/, worker/, wherever each fact
belongs. Use that one after doing the work; use this one after reading someone's note about it.
Finding the handoff
If /read-handoff already ran this session, use the file it picked up -- do not go looking again.
Otherwise find it exactly the way read-handoff does (read that skill rather than reimplementing
the search). An argument to this skill overrides all of it: a path is read directly, anything else
is treated as a project name.
Read the whole file before writing anything. A fact near the bottom often explains why a decision near the top was made, and only the pair is worth recording.
Which repository
- The
AGENTS.mdfiles you will write live undergit rev-parse --show-toplevel-- the working tree, which inside a git worktree is the worktree, not the main checkout. That is correct:AGENTS.mdis a tracked file, so it is checked out here and commits from here - Only the handoff's file name uses
--git-common-dir. Do not use it to place files
If the handoff was written about a different repository than the one you are in, stop and say so. Do not fold one project's facts into another's.
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 · 163 lines · 83 tokens per session scan A fa48a24a5354
apply-handoff-to-agents-md is a skill published in the GitHub repository aiya000/dotfiles (21 stars, last pushed 2d ago), licensed MIT. It adds 83 tokens to every session and 2,104 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-07.
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.