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/irachrist1/claude-code-workflow-os/handoff-operatornpx skills add irachrist1/claude-code-workflow-os --skill handoff-operatorgit clone --depth 1 https://github.com/irachrist1/claude-code-workflow-osWrote 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/irachrist1/claude-code-workflow-os/handoff-operator)<a href="https://agentmods.dev/skills/irachrist1/claude-code-workflow-os/handoff-operator"><img src="https://agentmods.dev/badge/skills/irachrist1/claude-code-workflow-os/handoff-operator.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.00034 | $0.00213 |
| Opus 5 | $0.00017 | $0.00106 |
| Sonnet 5 | $0.00007 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
handoff-operator 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 5d 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.
What it actually says
Handoff Operator
This repository uses handoff snapshots to preserve working context.
When ending a meaningful session
- Capture a handoff if the work is incomplete, risky, or likely to continue later.
- Prefer writing the handoff into
context/handoffs/instead of leaving critical context only in chat history.
When starting work from an existing repo
- Check for
context/handoffs/. - If a recent handoff exists, read it before broad implementation work.
- Treat the handoff as the fastest path to continuity, then verify against the repository state.
Handoff quality standard
A good handoff answers:
- What are we trying to achieve?
- What already changed?
- What is risky or broken?
- What should happen next?
- Which files matter first?
Keep handoffs short, direct, and operational.
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.
- 5d ago First seen · 33 lines · 34 tokens per session scan A 8a5939bdd9ee
handoff-operator is a skill published in the GitHub repository irachrist1/claude-code-workflow-os (2 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 213 once invoked, about $0.0002 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…