Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/egregore-labs/egregore/main/.claude/skills/handoff/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/handoff)<a href="https://agentmods.dev/skills/egregore-labs/egregore/handoff"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/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/egregore-labs/egregore/handoff"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 35 Subtle instructions detected that may alter agent decision-making or introduce hidden biases.Fix: Review content for implicit steering or bias. Ensure instructions are explicit and align with the skill's stated purpose.
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.00068 | $0.01462 |
| Opus 5.5 | $0.00027 | $0.00585 |
| Sonnet 5.5 | $0.00014 | $0.00292 |
| Haiku 4.5 | $0.00007 | $0.00146 |
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 24d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Internal team handoff
Create one typed handoff in memory/handoffs/. Canonical Markdown and Git
provenance are authoritative. Runtime owns authorization, stable identity,
persistence, provenance, retrieval refresh, background embedding, and
content-free telemetry.
Use this only for internal handoffs. Route external capsules to /emissary,
pending-work triage to /activity, and personal closure to /wrap.
When to invoke
Create an internal Egregore team handoff to a teammate or future self. Use when the user says /handoff, asks to pass work or context, or wants an operational continuation record. Route external or executable capsules to /emissary, pending-work triage to /activity, and personal closure to /wrap.
Bounded capture
A handoff records known context; it is not a research, audit, planning, or verification ritual.
- Use the user's prompt, current conversation, and attached
EGREGORE_ORG_CONTEXT_V1. When that context is attached, do not repeat organizational retrieval. - If no organizational context is attached and the requested handoff semantically depends on prior organizational work that is absent from the conversation, follow the actor context's one Runtime/QMD recall instruction. This is the only allowed retrieval: use its returned evidence without a second query or opening more sources.
- Do not otherwise search, inspect Git, read repository files, query migration/skill manifests, run status/tests, or spawn agents to improve the handoff.
- Include branches, files, decisions, tests, and remaining work only when already known from those inputs. Label uncertainty briefly; if the handoff cannot be drafted responsibly, ask one focused question instead of exploring.
- “To myself” resolves to
Actor display namein the attachedEGREGORE_ACTOR_CONTEXT_V1. Never infer it from the OS username, Git, or GitHub. If that block is unavailable, ask for the handle rather than guessing. Do not perform a people-directory lookup. Ask once only for a genuinely ambiguous teammate. - Infer
intent:action,feedback, orfyi.
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.
- 24d ago Changed · -255 lines · +14 tokens per session scan B → A 2cf3693d14b5
- 1mo ago First seen · 403 lines · 54 tokens per session scan B af78aec221ab
handoff is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 68 tokens to every session and 1,462 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-08-30.
Other skills, from other repositories
handoff-protocols
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or…
parallel-investigation
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist…
structured-code-review
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR…
bothread
Join and behave correctly in a Bothread room — a shared, human-governed space where you collaborate with other AI agents on one codebase. Use this when the user says they want you to join a Bothread session, gives you a Bothread session ID, or asks you to coordinate with other agents.
git-workflow
Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.
mflow
Use when working in a repo that uses mflow, coordinating multiple AI agents/worktrees, setting up mflow sync, installing mflow MCP in Codex/Claude Code/Cursor/opencode, or before git operations where synced file changes may affect commits. Applies to CLI, MCP, room secrets, pause/resume, locks, status checks, and safe…