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 ykorovko/dotagents --skill handoffgit clone --depth 1 https://github.com/ykorovko/dotagentsWrote 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/ykorovko/dotagents/handoff)<a href="https://agentmods.dev/skills/ykorovko/dotagents/handoff"><img src="https://agentmods.dev/badge/skills/ykorovko/dotagents/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/ykorovko/dotagents/handoff"><img src="https://agentmods.dev/badge/skills/ykorovko/dotagents/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.00041 | $0.00504 |
| Opus 5.5 | $0.00016 | $0.00202 |
| Sonnet 5.5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
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 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.
What it actually says
Handoff
Write a short handoff that lets a fresh agent continue without rereading the current conversation.
Put it somewhere the next session can open. Use a location supplied by the user first. If both sessions share a filesystem, create a unique file in the operating system's temporary directory using the environment's temp facility. Do not hard-code a path. For an isolated or remote harness, use durable artifact storage if the harness provides it. If nothing will persist between sessions, include the full handoff in the response and say that no file was created. Do not write it into the workspace unless the user asks.
Start with the user's goal and where the work stands. Keep the decisions and constraints that still affect the task. Note what is finished, what remains, which checks have run, and anything blocking progress. End with the next concrete action. If earlier parts of the conversation are unavailable, name the missing context instead of guessing.
For repository work, include the repository name or remote, branch, HEAD commit, base or upstream branch when known, and the state of any uncommitted work. Add the workspace root when it helps. Prefer paths relative to the repository so they still work after moving the project to another machine.
Point to existing plans, specifications, ADRs, issues, commits, diffs, and generated files by path or URL. Do not copy their contents into the handoff.
Add a section called Suggested skills. Name only skills known to be available to the next agent, and say briefly why each one would help. Installing or naming a skill does not load it automatically.
Remove secrets, credentials, personal data, and private context unrelated to the task.
If the user describes what the next session will focus on, shape the handoff around that focus. After writing a file, return its absolute path or artifact link with a one-sentence summary. If the handoff is inline, label it so the user can copy it into the next session. Creating the document does not start or message another agent unless the user asks for that separately.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 25 lines · 41 tokens per session scan A 697092a5e525
handoff is a skill published in the GitHub repository ykorovko/dotagents (0 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 504 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-08-31.
Other skills, from other repositories
greenfield
Parallel persona planning for new projects. Research agent runs first to build domain context, then Architect, PM, and Security agents run in parallel. Synthesis agent combines all perspectives into a detailed GSD-style PLAN.md with Tensions section.
brownfield-drift
Enforces architecture boundaries defined in PLAN.md. Use when a PR crosses module/service boundaries, when the dev asks "are we following the architecture?", or as a scheduled architecture health check. Not for querying what a module does — use brownfield-chat for that.
pr-review
Fix engine for PR review comments. Fetches review comments (Gemini bot or human), categorizes by impact, posts a prioritized fix queue, and applies fixes on dev approval. Called directly for quick fixes, or internally by pr-review-agent as part of full PR review.
wednesday-git
Unified Git workflow. Manages the entire task lifecycle: branch creation (sprint), atomic commits (git-os), and PR opening (pr-create).
standards-kit
Unified development and design standards. Enforces code quality (complexity < 8), strict naming conventions, and the mandatory use of approved UI component libraries.
pixeltamer
Generate, edit, and compose images with GPT Image 2.5, including transparent PNGs with a real alpha channel. Two backends — OpenAI API key or codex CLI (uses your ChatGPT subscription, no key needed). Four modes — one-shot generate, edit or inpaint an existing image, multi-reference composition (up to 16 inputs…