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 decline-handoff-suggestiongit 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/decline-handoff-suggestion)<a href="https://agentmods.dev/skills/aiya000/dotfiles/decline-handoff-suggestion"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/decline-handoff-suggestion/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/decline-handoff-suggestion"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/decline-handoff-suggestion.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.00061 | $0.00619 |
| Opus 5.5 | $0.00024 | $0.00248 |
| Sonnet 5.5 | $0.00012 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
decline-handoff-suggestion 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 17d 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
decline-handoff-suggestion
The one-word answer to the question offer-handoff.sh asks at session start. It exists so the
user can say "no" with a completion instead of a sentence.
Declining leaves an empty <name>.declined next to <name>.md. The hook skips a handoff that has
one, so that handoff is not offered again -- a newer one still is. The marker does not end in
.md, so read-handoff can still read the file when asked.
Finding the file
The same file the hook offered -- keep this in step with .claude_global/hooks/offer-handoff.sh:
-
The directories, searched together:
~/.ai-memory/handoff/(wherecreate-handoffwrites now), and the old local places~/tmp/claude-handoff/and${TMPDIR:-/tmp}/claude-handoff/ -
The project:
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>-*.mdacross them, sorted by file name..dotfileshandoffs start with a dot, so usels -aor a glob, not a plainls -
If there is none for this project, say so and stop. Do not fall back to another project's file -- the hook never offers those, so there is nothing to decline
An argument overrides all of that: a path is taken directly, anything else is treated as a project name.
Marking it
touch <dir>/<name>.declined--<name>is the handoff's file name without.md- When the handoff is in
~/.ai-memory/handoff/, publish the marker with thesync-memoryskill --publish 'handoff: decline <name>' handoff/<name>.declined-- so the other machine does not offer it either, and the marker does not sit untracked in the repository
- When the handoff is in
- Do not read the handoff. Declining is the whole job
- Say in one line which handoff was declined. If it was already declined, say that instead; the
touchis harmless either way
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.
- 17d ago Changed 3bbfb11d495a
- 20d ago First seen · 46 lines · 61 tokens per session scan A 899bf815477c
decline-handoff-suggestion is a skill published in the GitHub repository aiya000/dotfiles (21 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 619 once invoked, about $0.0002 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.