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 saemihemma/lead-producer-oss --skill workflow-session-handoffgit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/workflow-session-handoff)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/workflow-session-handoff"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-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/saemihemma/lead-producer-oss/workflow-session-handoff"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-session-handoff.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.00629 |
| Opus 5 | $0.00028 | $0.00315 |
| Sonnet 5 | $0.00011 | $0.00126 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
workflow-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 8d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff Workflow
Purpose
Turn a long or finishing session into a self-contained handoff the next agent can resume from cold, without re-reading the whole transcript. The artifact is the deliverable.
Use When
- A session is ending and work is unfinished
- Passing a task to another agent or a future session
- Context is large and the next step should start from a clean summary
- The user asks to "hand off," "wrap up," or "summarize for next time"
Do NOT Use When
- Mid-session context is degrading and the fix is in-session checkpointing or pruning (use
role-context-manager) - The goal is to orient a new owner to a system rather than continue this work (use
workflow-current-state-capture) - The work is a bug needing a reproduction-and-fix package (use
workflow-issue-triage)
Boundary vs role-context-manager
role-context-manager manages context within a live session (checkpointing, hygiene, preventing degradation). This workflow produces an end-of-session export for whoever picks up next. Use context-manager to keep going; use handoff to stop cleanly.
Working Method
- Summarize the goal and the current state in a few sentences.
- List what was done — decisions made, files changed, commits/branches, artifacts produced.
- List what is open — unfinished threads, blockers, unresolved questions.
- Name the next steps concretely, and suggest which skills/specialists the next agent should route through.
- Redact secrets. Never copy tokens, keys, or credentials into the artifact.
- Persist to
_artifacts/handoff-<slug>.md(ask where to save if_artifacts/does not exist).
Default Artifact
Persist to _artifacts/handoff-<slug>.md.
SESSION HANDOFF
===============
Goal: what this work is trying to achieve
Current State: where things stand right now
Done: decisions, changes, commits/branches, artifacts
Open: unfinished threads, blockers, unresolved questions
Next Steps: concrete actions, in order
Suggested Skills: which roles/teams/workflows the next agent should route via LP
Pointers: key files, paths, and artifacts (no secrets)
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.
- 8d ago First seen · 52 lines · 55 tokens per session scan A a9bf99ac265b
workflow-session-handoff is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 8d ago), licensed MIT. It adds 55 tokens to every session and 629 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-09-03.
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…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
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.