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 Adit-Jain-srm/skill-forge --skill handoffgit clone --depth 1 https://github.com/Adit-Jain-srm/skill-forgeWrote 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/adit-jain-srm/skill-forge/handoff)<a href="https://agentmods.dev/skills/adit-jain-srm/skill-forge/handoff"><img src="https://agentmods.dev/badge/skills/adit-jain-srm/skill-forge/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.1 | $0.00059 | $0.00669 |
| Opus 5 | $0.00030 | $0.00334 |
| Sonnet 5 | $0.00012 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
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 7d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Create a structured document capturing everything needed to continue work in a fresh session — in under 50 lines.
Process
Write a handoff document capturing everything needed to continue this work.
What to Include
1. GOAL — what we're building/fixing (one sentence)
2. CURRENT STATE — what's done, what's in progress, what's blocked
3. KEY DECISIONS MADE — choices that shouldn't be re-litigated
4. OPEN QUESTIONS — unresolved decisions awaiting input
5. NEXT STEPS — exact actions to take (not vague "continue working")
6. FILES TOUCHED — paths modified this session
7. SUGGESTED SKILLS — which skills the next session should invoke
What NOT to Include
- Full code (reference by file path instead)
- Conversation history (this is a SUMMARY not a transcript)
- Sensitive info (API keys, passwords, PII)
- Resolved dead ends (only include what's RELEVANT going forward)
Where to Save
Save to the OS temp directory (not the workspace):
- Windows:
$env:TEMP/handoff-{project}-{date}.md - macOS/Linux:
/tmp/handoff-{project}-{date}.md
Tell the user the path so they can reference it next session.
Common Mistakes
- Including full code instead of file paths (bloats the handoff, makes it unreadable)
- Forgetting open questions (next session re-litigates decisions)
- Writing vague next steps like "continue working" (be SPECIFIC: which file, which function, which test)
- Saving to the workspace (pollutes the project — use temp directory)
Format
Keep it SHORT. Under 50 lines. A good handoff is one page a new agent can scan in 10 seconds and know exactly what to do.
Example
## Handoff — skill-forge v1.2.0
**Goal:** Add TF-IDF semantic routing to replace token-overlap matching.
**State:** Route-task.js rewritten and passing. 98 tests green. Not yet pushed.
**Decisions Made:**
- TF-IDF + cosine similarity (not embedding API — zero dependencies)
- Compound routing: combine top 3-5 skills when overlap < 40%
- Indexed learnings surfaced alongside skill matches
**Open Questions:**
- Should RL weights be per-skill or per-category? (currently per-category)
**Next Steps:**
1. Run `node tests/run-tests.js` — confirm all pass
2. Push with `git -c http.version=HTTP/1.1 push origin main`
3. Update SKILL.md Phase 4 to reference new routing
**Files:** scripts/route-task.js, memory/indexed-learnings.json, tests/run-tests.js
**Skills for next session:** /prove-it, /self-review
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.
- 7d ago First seen · 81 lines · 59 tokens per session scan A 0ae19360aec2
handoff is a skill published in the GitHub repository Adit-Jain-srm/skill-forge (2 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 669 once invoked, about $0.0003 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-31.
Other skills, from other repositories
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
user-research-cookiy
End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment…
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.
daily-journal
A passive daily work journal that Claude keeps FOR you so you never have to write it yourself. Append short entries after meaningful work (what was done, what you focused on, artifacts touched) to 01-daily/journal/YYYY-MM-DD.md. Run a guided reflection at night or in the morning. Use when you run /daily-journal, say…
ijfw-handoff
Session handoff generation and loading. Trigger: session end, context full, /handoff.