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 HigorAlves/orc --skill handoffgit clone --depth 1 https://github.com/HigorAlves/orcWrote 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/higoralves/orc/handoff)<a href="https://agentmods.dev/skills/higoralves/orc/handoff"><img src="https://agentmods.dev/badge/skills/higoralves/orc/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/higoralves/orc/handoff"><img src="https://agentmods.dev/badge/skills/higoralves/orc/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.00052 | $0.00276 |
| Opus 5.5 | $0.00021 | $0.00110 |
| Sonnet 5.5 | $0.00010 | $0.00055 |
| Haiku 4.5 | $0.00005 | $0.00028 |
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 4d 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.
This is a copy
81% identical to handoff — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS ($TMPDIR, else /tmp; %TEMP% on Windows) — never the current workspace — and report the absolute path.
Include a "suggested skills" section in the document, naming which orc: skills and commands the next agent can invoke.
Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
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.
- 4d ago Changed 8894d7c3f2d4
- 1mo ago First seen · 21 lines · 52 tokens per session scan A dc4accfb3401
handoff is a skill published in the GitHub repository HigorAlves/orc (7 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 276 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to handoff, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
scout-briefing
Launch a Scout morning briefing session as a background process. Auto-detects mode (morning briefing, consolidation, or weekend briefing) from the current time and day.
scout-dream
Launch a Scout dreaming session as a background process. Processes feedback, does KB deep work, and works on wishlist items.
autonomous
Run multiple phases hands-free. Chains discuss, plan, build, and verify automatically.
resume
Pick up where you left off. Restores context and suggests next action.
g-listen
Enter listen mode — collect user reports and information without acting, then synthesize and triage when the user signals done.
continue
Execute the next logical step automatically. No prompts, no decisions — just do it.