Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sofumel/claude-handoff-revive/plugin install handoff-reviveWrote 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/commands/sofumel/claude-handoff-revive/share-to-pr)<a href="https://agentmods.dev/commands/sofumel/claude-handoff-revive/share-to-pr"><img src="https://agentmods.dev/badge/commands/sofumel/claude-handoff-revive/share-to-pr.svg" alt="Measured on agentmods" 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.00031 | $0.00352 |
| Opus 5 | $0.00015 | $0.00176 |
| Sonnet 5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
share-to-pr 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 7d 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.
What it actually says
Share .claude/handoff/current.md to a GitHub PR as a comment. This publishes the handoff content externally — always show the user what will be posted and get an explicit yes before posting.
Steps:
- Run the dry-run first (pass the user's PR number
$ARGUMENTSif given; otherwise the script auto-detects the current branch's PR):- Linux/macOS/WSL/Git-Bash:
bash "${CLAUDE_PLUGIN_ROOT:-.claude}/skills/handoff-revive/scripts/share-to-pr.sh" --dry-run [PR] - Windows PowerShell:
$r = if ($env:CLAUDE_PLUGIN_ROOT) { $env:CLAUDE_PLUGIN_ROOT } else { ".claude" }; powershell -ExecutionPolicy Bypass -File "$r/skills/handoff-revive/scripts/share-to-pr.ps1" -DryRun [-Pr <PR>]
- Linux/macOS/WSL/Git-Bash:
- Show the user (in their language, read
.claude/handoff/lang) which PR it will go to and the body preview. Warn that the handoff may contain absolute paths or other local details and point out anything that looks sensitive. - Only after the user confirms, run the same command without
--dry-run/-DryRun. - Report the result. If
ghis missing or no PR exists for the branch, relay the script's error and stop.
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.
- 7d ago First seen · 22 lines · 31 tokens per session scan A 8710812d35a1
share-to-pr is a command published in the GitHub repository sofumel/claude-handoff-revive (6 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 352 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 commands, from other repositories
resolve-pr
Resolve PR review feedback — fetch unresolved threads, triage, dispatch resolver agents, reply + resolve via GraphQL.
code-review
Review someone else's open GitHub PR — posts a real review with line-anchored inline comments; verdict computed mechanically; mandatory preview gate. Workspace-aware. For your OWN working diff, prefer the bundled /code-review instead.
address
Answer reviewer comments on YOUR open PR — categorize unresolved threads, push fixes, and post replies. Workspace-aware across linked PRs.
coordination-audit
Run a pre-merge coordination audit — checks PR readiness, review state, merge queue hygiene, and local review policy before merger proceeds.
check-pr
Check the current branch's PR for external review feedback, fix errors and warnings, run a final external review, and push.
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.