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 janrummel/claude-orchestrator-starter --skill handoffgit clone --depth 1 https://github.com/janrummel/claude-orchestrator-starterWrote 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/janrummel/claude-orchestrator-starter/handoff)<a href="https://agentmods.dev/skills/janrummel/claude-orchestrator-starter/handoff"><img src="https://agentmods.dev/badge/skills/janrummel/claude-orchestrator-starter/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/janrummel/claude-orchestrator-starter/handoff"><img src="https://agentmods.dev/badge/skills/janrummel/claude-orchestrator-starter/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.00070 | $0.00927 |
| Opus 5 | $0.00035 | $0.00464 |
| Sonnet 5 | $0.00014 | $0.00185 |
| Haiku 4.5 | $0.00007 | $0.00093 |
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 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff — Save Session State
You save the current work state so the next session can continue seamlessly. No context is lost.
Core Principles
- Write for your future self — assume NOTHING from this session is known
- Decisions with reasoning — not just WHAT, but WHY
- Record discarded alternatives — prevents repetition
- Concrete next steps — specific enough to start immediately
Workflow
Step 1: Identify Project
Which project was active in this session?
Existing state file?
ls ~/.claude/orchestrator/projects/
- Yes: Load and update state file
- No: Create new state from template
Determine project name:
- Derive from context (directory, topic, user input)
- Use kebab-case:
my-project,research-topic,feature-name
Step 2: Summarize Session
Analyze the current session and extract:
2a. Active Context (MOST IMPORTANT section)
- Where are we right now? (2-5 bullet points)
- What was the main topic?
- What was achieved?
- What is the immediate next step?
2b. Decisions For EACH decision made in this session:
- What was chosen?
- Why? (1-2 sentences reasoning)
- Which alternatives were discarded and why?
2c. Open Questions
- What remained unclear?
- What needs to be decided next session?
- Where are there uncertainties?
2d. Next Steps
- Prioritized list of concrete actions
- Specific enough to start immediately
- First action should be doable without further questions
2e. Relevant Files
- Which files were created/modified?
- Which files are important for continued work?
Step 3: Write State File
Save/update state file at:
~/.claude/orchestrator/projects/<projectname>.md
Template:
# Project: [Name]
## Active Context
- [Current state point 1]
- [Current state point 2]
## Decision Trail
### [Date] — [Decision Title]
- **Chosen:** [What]
- **Reasoning:** [Why]
- **Discarded:** [Alternatives and why not]
## Open Questions
- [ ] [Question 1]
- [ ] [Question 2]
## Next Steps
1. [Highest priority action]
2. [Second priority action]
3. [Third priority action]
## Relevant Files
| File | Purpose |
|------|---------|
| `path/to/file` | [What it contains] |
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 · 140 lines · 70 tokens per session scan A 0bbcf5908614
handoff is a skill published in the GitHub repository janrummel/claude-orchestrator-starter (5 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 927 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
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…
vellum-memory-v2-migration
Perform a one-time migration from memory v1, to memory v2, which was introduced in 0.8.0.
vellum-memory-v3-migration
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…
ha-knowledge
Working method for the Hope Agent knowledge space — how to capture, organize, link, retrieve, and maintain Markdown notes well with the note tools. Load whenever you are reading or writing notes in an attached knowledge base. Trigger on: user asks to take / save / organize / restructure notes, build or grow a…
okf
Author, maintain, and consume Open Knowledge Format (OKF) knowledge bundles — portable markdown + YAML frontmatter that both humans and agents read. Use when capturing project knowledge (services, APIs, schemas, metrics, runbooks, decisions) into an OKF bundle, when updating one after code or docs change, or when a…