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 hoblin/claude-ruby-marketplace --skill resume_handoffgit clone --depth 1 https://github.com/hoblin/claude-ruby-marketplaceWrote 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/hoblin/claude-ruby-marketplace/resume_handoff)<a href="https://agentmods.dev/skills/hoblin/claude-ruby-marketplace/resume_handoff"><img src="https://agentmods.dev/badge/skills/hoblin/claude-ruby-marketplace/resume_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/hoblin/claude-ruby-marketplace/resume_handoff"><img src="https://agentmods.dev/badge/skills/hoblin/claude-ruby-marketplace/resume_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.00011 | $0.01939 |
| Opus 5 | $0.00005 | $0.00970 |
| Sonnet 5 | $0.00002 | $0.00388 |
| Haiku 4.5 | $0.00001 | $0.00194 |
Grade A, and why
resume_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.
How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume work from a handoff document
You are tasked with resuming work from a handoff document through an interactive process. These handoffs contain critical context, learnings, and next steps from previous work sessions that need to be understood and continued.
Initial Response
When this command is invoked:
-
If the path to a handoff document was provided:
- If a handoff document path was provided as a parameter, skip the default message
- Immediately read the handoff document FULLY
- Immediately read any research or plan documents that it links to under
./thoughts/shared/plansor./thoughts/shared/research. do NOT use a sub-agent to read these critical files. - Begin the analysis process by ingesting relevant context from the handoff document, reading additional files it mentions
- Then propose a course of action to the user and confirm, or ask for clarification on direction.
-
If a ticket number (like ENG-XXXX) was provided:
- run
thoughts-syncto ensure your./thoughts/directory is up to date. - locate the most recent handoff document for the ticket. Tickets will be located in
./thoughts/shared/handoffs/ENG-XXXXwhereENG-XXXXis the ticket number. e.g. forENG-1234the handoffs would be in./thoughts/shared/handoffs/ENG-1234/. List this directory's contents recursively (handoffs are in date subdirectories likeYYYY-MM-DD/). - There may be zero, one or multiple files across the date subdirectories.
- If there are zero files, or the directory does not exist: tell the user: "I'm sorry, I can't seem to find that handoff document. Can you please provide me with a path to it?"
- If there is only one file: proceed with that handoff
- If there are multiple files: using the date from the subdirectory name (
YYYY-MM-DD) and time from the filename (HH-MM-SS), proceed with the most recent handoff document. - Immediately read the handoff document FULLY
- Immediately read any research or plan documents that it links to under
./thoughts/shared/plansor./thoughts/shared/research; do NOT use a sub-agent to read these critical files. - Begin the analysis process by ingesting relevant context from the handoff document, reading additional files it mentions
- Then propose a course of action to the user and confirm, or ask for clarification on direction.
- run
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 First seen · 219 lines · 11 tokens per session scan A bbfda56579e7
resume_handoff is a skill published in the GitHub repository hoblin/claude-ruby-marketplace (37 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 1,939 once invoked, about $0.0001 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-07.
Other skills, from other repositories
plan-orchestrator
Route hierarchical-planning intents to the correct backing script. Use when the user invokes /aura-frog:plan (with or without subcommand), mentions plan verbs (expand/next/replan/promote/archive/freeze/thaw/undo/status/conflicts), or types a plan-vocabulary bare word with .claude/plans/active.json present. Owns verb…
conflict-detector
L1-L4 conflict detection between a proposed T4 task and pending-confirm sibling tasks. L1 (file overlap) + L2 (function/region overlap) ship in v3.7.0-beta.2 as deterministic bash. L3 (semantic LLM) + L4 (architectural LLM) are stubbed for v3.7.0-rc.1.
plan-loader
Loads minimum hierarchical plan context (.claude/plans/) for current execution focus. Auto-invokes every session when plans exist. Stays under 800 always-loaded tokens regardless of plan tree size.
wrap-up
End-of-session handler that first checks whether the current session's plan is actually complete. If complete: run a quick retrospective, emit a forward-looking follow-up prompt, and — in a git repository — refresh the repo and clean gone branches. If incomplete: skip cleanup and emit ready-to-paste resume prompts so…
issue-sweep
Use when a tracker's open issues have piled up, gone stale, or stopped reflecting reality — issues that may already be fixed, duplicated, vague, or superseded — and you want them reconciled against the actual code and system, grouped by root cause, and turned into a plan for the highest-value cluster. Works with any…
track-followups
Record triaged follow-up work where it will actually be seen — create the item in the issue tracker (Vikunja) or the incident system of record (Zammad), deduplicating first and reporting the created identifier. Use when a session produced work that outlives it, or when another skill has triaged items and needs them…