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 agentmods add skills/drvoss/everything-copilot-cli/handoffnpx skills add drvoss/everything-copilot-cli --skill handoffgit clone --depth 1 https://github.com/drvoss/everything-copilot-cliWrote 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/drvoss/everything-copilot-cli/handoff)<a href="https://agentmods.dev/skills/drvoss/everything-copilot-cli/handoff"><img src="https://agentmods.dev/badge/skills/drvoss/everything-copilot-cli/handoff.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.01575 |
| Opus 5 | $0.00020 | $0.00788 |
| Sonnet 5 | $0.00008 | $0.00315 |
| Haiku 4.5 | $0.00004 | $0.00158 |
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 today.
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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Handoff turns the current state of work into a portable markdown brief that another session, agent, or collaborator can pick up quickly.
The goal is not "summarize everything." The goal is to capture only the information that would otherwise be expensive to rediscover.
When to Use
- You are ending a session but the work is not actually finished
- Another agent, model, or machine will continue the task
- The conversation contains decisions that are not yet reflected in committed files
- A reviewer or implementer needs a compact state-of-play document
When NOT to Use
| Instead of handoff | Use |
|---|---|
| Continuing the same Copilot CLI session later | cross-session-memory or /resume |
| Recording durable project guidance for everyone | knowledge-curator |
| Writing a committed spec, ADR, PRD, or issue | the destination artifact itself |
Workflow
1. Clarify what the next session is for
Start with one sentence:
- what the next session should accomplish
- what is already done
- what remains uncertain
If the user gave a follow-up goal, tailor the handoff around that goal instead of the whole conversation.
2. Pick a portable file path
Prefer a temporary markdown file outside the repo unless the user explicitly wants a committed file.
Examples:
# PowerShell
$path = Join-Path $env:TEMP ("handoff-" + [System.Guid]::NewGuid().ToString("N") + ".md")
# POSIX shell
path="$(mktemp -t handoff-XXXXXX.md)"
If a path already exists, read it before overwriting.
3. Reference artifacts instead of duplicating them
Do not restate content that already lives in:
- a plan
- an issue
- a PR
- an ADR
- a committed file
- a benchmark result
Link to those artifacts by path, URL, or commit hash and explain only why they matter.
3-A. Redact sensitive data before saving
Before writing the handoff document, actively redact sensitive data in the captured context:
- API keys, tokens, or credentials ->
[REDACTED] - Passwords or secrets ->
[REDACTED] - PII in sensitive context ->
[REDACTED] - Internal-only URLs or endpoints ->
[INTERNAL URL]
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.
- today First seen · 239 lines · 40 tokens per session scan A 6d9738c934db
handoff is a skill published in the GitHub repository drvoss/everything-copilot-cli (45 stars, last pushed 8d ago), licensed MIT. It adds 40 tokens to every session and 1,575 once invoked, about $0.0002 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-03.
Other skills, from other repositories
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
manage-project
Research project management for medical manuscripts. Scaffold project structure, track writing progress across phases, maintain project memory files, generate submission checklists and backwards timelines. Commands: init, status, sync-memory, checklist, timeline.
harness-step3-session-management
Harness Engineering 第二阶段：建立跨 session 状态管理，解决 agent 每次对话失忆的问题。 创建 tasks.json（任务清单）、progress.md（进度记录）、init.sh（环境初始化脚本）三个文件。 当用户说"建立任务管理"、"让 agent 记住进度"、"创建 tasks.json"、"跨 session 保持状态"、 "agent 每次都不记得上次做了什么"、"建立 progress 文件"、"初始化状态管理"时，立即使用此 skill。 前置条件：harness-step1 和 harness-step2 已完成（项目有 AGENTS.md 和 docs/ 知识库）。.
harness-design
Design and build multi-agent harness architectures for long-running AI application development. GAN-inspired Generator-Evaluator pattern, Sprint Contract negotiation, context management, quality criteria calibration. Based on Anthropic Engineering patterns. Use when: "build a harness", "multi-agent architecture"…
okf-pro
Operating rules for the .okf/ knowledge bundle — filing new concepts, the board, the journal, the daily snapshot, closing work, source attribution, and the generated/verified attestation policy. Use before reading from or writing anything into .okf/.
project-butler
Project memory workflow for init/upgrade, profile-aware setup, end session, normal/full close, file organization, document archiving, language switching, versioned update logs, rule review, status, wiki sync, and context recovery. Use for /project-butler, setup/初始化, foundation setup, profile setup, end session/收工…