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 juicesharp/rpiv-mono --skill resume-handoffgit clone --depth 1 https://github.com/juicesharp/rpiv-monoWrote 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/juicesharp/rpiv-mono/resume-handoff)<a href="https://agentmods.dev/skills/juicesharp/rpiv-mono/resume-handoff"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/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/juicesharp/rpiv-mono/resume-handoff"><img src="https://agentmods.dev/badge/skills/juicesharp/rpiv-mono/resume-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.02062 |
| Opus 5 | $0.00040 | $0.01031 |
| Sonnet 5 | $0.00016 | $0.00412 |
| Haiku 4.5 | $0.00008 | $0.00206 |
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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- resume-handoff — 86% identical, 112 lines differ
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume Handoff
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.
Input
$ARGUMENTS — path to a handoff document under .rpiv/artifacts/handoffs/. If omitted, the skill lists available handoffs and asks which to resume from.
Metadata
echo "### recent (read only in case of empty user input)"
echo "recent handoffs:"
node "${SKILL_DIR}/../_shared/list-recent.mjs" .rpiv/artifacts/handoffs 10
Flow
- Input → 2. Read & analyze handoff → 3. Synthesize & present → 4. Create action plan → 5. Begin implementation
Steps
Step 1: Input Handling
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 using the Read tool
- Immediately read any research or plan documents that it links to under
.rpiv/artifacts/plansor.rpiv/artifacts/researchor.rpiv/artifacts/solutions. Read these critical files DIRECTLY using the Read tool - do NOT invoke skills for this initial reading phase. - 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 no parameters provided, branch on the
recent handoffs:listing in the Metadata block:- Empty — no handoffs exist; tell the user and ask for a path in prose.
- Exactly one entry — confirm with
ask_user_question: "Resume this handoff?" with options "Resume<filename>(Recommended)" and "Pick a different path". Do NOT callask_user_questionwith a single option (the tool requires ≥2). - Two or more entries — present the top 4 filenames as
ask_user_questionoptions. The tool automatically appends aType something.free-text row; do not list it manually.
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.
- 12d ago First seen · 230 lines · 80 tokens per session scan A 45fcfd16c6eb
resume-handoff is a skill published in the GitHub repository juicesharp/rpiv-mono (780 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 2,062 once invoked, about $0.0004 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.