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 zarpay/rails-template --skill handoff-resumegit clone --depth 1 https://github.com/zarpay/rails-templateWrote 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/zarpay/rails-template/handoff-resume)<a href="https://agentmods.dev/skills/zarpay/rails-template/handoff-resume"><img src="https://agentmods.dev/badge/skills/zarpay/rails-template/handoff-resume/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/zarpay/rails-template/handoff-resume"><img src="https://agentmods.dev/badge/skills/zarpay/rails-template/handoff-resume.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.00038 | $0.00778 |
| Opus 5 | $0.00019 | $0.00389 |
| Sonnet 5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
superpowers-ruby:handoff-resume 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff Resume
Overview
Resume work from a previously created handoff document. Finds the latest unrestored handoff, reads it, marks it as consumed, archives it, and sets up the session to continue from where the previous session left off.
Core principle: Read the handoff, understand the context, then continue from Next Steps.
Announce at start: "I'm using the handoff-resume skill to restore session context."
When to Use
- Starting a new session to continue previous work
- After a session was ended without completing work
- When a colleague or agent left a handoff for you
- When you see handoff documents exist in
docs/handoffs/
Don't use when:
- Context was just compacted (the
PostCompacthook handles this automatically) - There is no handoff document to resume from
The Process
Step 1: Find Unrestored Handoffs
# Look for handoff files with restored: false
ls docs/handoffs/*.md 2>/dev/null
Read each file's frontmatter and filter for restored: false. Sort by created date, newest first.
Step 2: Select Handoff
If one unrestored handoff exists: Use it automatically.
If multiple unrestored handoffs exist: Present them and ask which to resume:
Found multiple unrestored handoffs:
| # | Date | Topic | Branch |
|---|------|-------|--------|
| 1 | 2026-04-14 | handoff-skill | lg/handoff |
| 2 | 2026-04-13 | auth-refactor | fix/auth |
Which handoff should I resume from?
If no unrestored handoffs exist: Check the archive:
ls docs/handoffs/_archive/*.md 2>/dev/null
If archived handoffs exist, list them and offer to re-open one. If none exist at all, inform the user.
Step 3: Read and Present
Read the full handoff document. Present a summary:
Resuming from handoff: <topic>
- Branch: <branch>
- Created: <date>
- Goal: <goal summary>
- Next steps: <count> items
- Files to read: <count> documents
Step 4: Mark as Restored and Archive
Update the handoff file's frontmatter:
- Set
restored: true - Add
restored_at: <ISO 8601 UTC timestamp>
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 · 98 lines · 38 tokens per session scan A e1a96c38967b
superpowers-ruby:handoff-resume is a skill published in the GitHub repository zarpay/rails-template (9 stars, last pushed 29d ago), licensed MIT. It adds 38 tokens to every session and 778 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
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.