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/rohitg00/skillkit/handoff-protocolsnpx skills add rohitg00/skillkit --skill handoff-protocolsgit clone --depth 1 https://github.com/rohitg00/skillkitWhat 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.00116 | $0.01520 |
| Opus 5 | $0.00058 | $0.00760 |
| Sonnet 5 | $0.00023 | $0.00304 |
| Haiku 4.5 | $0.00012 | $0.00152 |
Grade A, and why
handoff-protocols 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 3d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff Protocols
You are executing a work handoff between team members or agents.
Handoff Types
| Type | When | Key Characteristics |
|---|---|---|
| Planned | End of shift, vacation, role change | Time to prepare docs; opportunity for sync meeting; gradual transition possible |
| Unplanned | Illness, emergency, priority change | Limited prep time; rely on existing docs; may need to reconstruct context |
| Partial | Transfer one piece while retaining other work | Requires clear boundary definition; shared ownership and integration points |
Handoff Document
Essential Sections
# Handoff: [Task/Project Name]
## Quick Summary
[One paragraph: What is this and current state]
## Current Status
- [ ] Phase: [Design/Implementation/Testing/etc]
- [ ] Progress: [X% complete / Y of Z tasks done]
- [ ] Blockers: [Current blockers, if any]
- [ ] Next Action: [Very next thing to do]
## Context
### What We're Building
[Brief description of the goal/feature]
### Why
[Business/technical justification]
### Key Decisions Made
| Decision | Options Considered | Choice | Rationale |
|----------|-------------------|--------|-----------|
| [D1] | A, B, C | B | [Why B was chosen] |
### Open Questions
- [Question 1]
- [Question 2]
## Technical Details
### Architecture/Design
[Relevant diagrams or links]
### Key Files
- `path/to/file1.ts` - [Purpose]
- `path/to/file2.ts` - [Purpose]
### Dependencies
- [Dependency 1]: [How it's used]
- [Dependency 2]: [How it's used]
## Current State of Code
### What's Complete
- [x] [Completed item 1]
- [x] [Completed item 2]
### In Progress
- [ ] [In progress item] - [Current state]
### Not Started
- [ ] [Pending item 1]
- [ ] [Pending item 2]
## Known Issues
### Active Issues
- [Issue 1]: [Description and current understanding]
### Workarounds in Place
- [Workaround 1]: [Why it exists, how to remove it]
## How to Continue
### Immediate Next Steps
1. [Step 1]
2. [Step 2]
3. [Step 3]
### Things to Watch Out For
- [Gotcha 1]
- [Gotcha 2]
### Who to Contact
- [Name/Team] for [Topic]
- [Name/Team] for [Topic]
## Resources
- [Link to design doc]
- [Link to requirements]
- [Link to related PRs]
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.
- 3d ago First seen · 257 lines · 116 tokens per session scan A dbaed32b84e4
handoff-protocols is a skill published in the GitHub repository rohitg00/skillkit (1,477 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 116 tokens to every session and 1,520 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.
init-workspace-context
Classify workspace mode.
context-engine
Performs hybrid semantic/lexical search with neural reranking for codebase retrieval. Use for finding implementations, Q&A grounded in source code, and cross-session persistent memory.
mcp-tool-selection
Decision rules for when to use MCP Qdrant-Indexer semantic search vs grep/literal file tools. Use this skill when starting exploration, debugging, or answering "where/why" questions about code.
workflows-create
Create a durable Zapier workflow from natural language using @zapier/zapier-durable and the Zapier SDK CLI. Use when the user wants to build a Zapier workflow, create an automation, write a durable workflow, build me a Zap that, create a durable that, or automate a multi-step process involving Zapier-connected apps.
workflows-modify
Modify and republish an existing durable workflow using the Zapier SDK experimental Code Workflows commands. Use when the user asks to fix my Zap, update my Zap, modify my workflow, repair this Zap, or edit a deployed Zapier workflow.