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 kraulerson/solo-orchestrator --skill session-handoffgit clone --depth 1 https://github.com/kraulerson/solo-orchestratorWrote 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/kraulerson/solo-orchestrator/session-handoff)<a href="https://agentmods.dev/skills/kraulerson/solo-orchestrator/session-handoff"><img src="https://agentmods.dev/badge/skills/kraulerson/solo-orchestrator/session-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/kraulerson/solo-orchestrator/session-handoff"><img src="https://agentmods.dev/badge/skills/kraulerson/solo-orchestrator/session-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.01033 |
| Opus 5 | $0.00026 | $0.00517 |
| Sonnet 5 | $0.00010 | $0.00207 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
session-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 10d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff
Attribution. This skill is adapted with permission from mattpocock/skills (MIT, © Matt Pocock). The original skill (
handoff) was written to be lightweight and tool-agnostic. This Solo Orchestrator-adapted version writes todocs/handoffs/so the handoff lives with the project as an auditable artifact (Solo's W7 handoff-readiness principle), and is namedsession-handoffto disambiguate from Solo's Phase 4 production HANDOFF.md (templates/generated/handoff.tmpl). SeeNOTICEfor full attribution and license.
When to use
Use before any of:
- Hard context-window break (the next reply might roll context out of memory).
- Machine reboot or planned shutdown.
- Switching to a different agent or operator mid-task.
- End-of-day stop when work is mid-flight and you want to resume cleanly tomorrow.
Do not use this skill for:
- Phase 4 production handoff to operations — that goes in
HANDOFF.mdvia the project's existingtemplates/generated/handoff.tmpl. They are different artifacts with different audiences. - Single-task summaries inside a session — write those inline.
What it produces
Write a markdown document summarizing the current conversation so a fresh agent (or future-you) can continue cleanly. Save it to:
docs/handoffs/YYYY-MM-DD-<topic-slug>.md
(Create docs/handoffs/ if it does not exist.)
The handoff document MUST include:
- Where we are — one-paragraph status of the work in progress: current branch, current PR (if any), current task on the implementation plan, current test-gate state.
- What just shipped this session — bullet list of commits / PRs / artifacts produced. Link to file paths and PR URLs, do not duplicate content.
- What's blocked / waiting — anything paused on user review, external state (CI, deploys), or unanswered design questions.
- What's next — the specific next concrete action. If multiple options exist, list them with the recommendation.
- References — paths to PRDs, plans, ADRs, specs, TRIAGE docs, calibration reports the next session will need. Use repo-relative paths.
- Resume prompt — a single paragraph the user can paste into the next session (or have an agent re-enter with) that re-establishes context. Should be self-contained: "Continuing from handoff at . . ."
What ships with it
1 file 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.
- 10d ago First seen · 66 lines · 51 tokens per session scan A 4e1ab3b5f62f
session-handoff is a skill published in the GitHub repository kraulerson/solo-orchestrator (29 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 1,033 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-30.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.