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 AaronCarney/pass-the-baton/plugin install pass-the-batonWrote 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/aaroncarney/pass-the-baton/renew)<a href="https://agentmods.dev/commands/aaroncarney/pass-the-baton/renew"><img src="https://agentmods.dev/badge/commands/aaroncarney/pass-the-baton/renew.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.00022 | $0.00301 |
| Opus 5 | $0.00011 | $0.00151 |
| Sonnet 5 | $0.00004 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
renew 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 8d 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
Arm an immediate checkpoint for this session:
!bash "${CLAUDE_PLUGIN_ROOT}/tools/baton-checkpoint-now.sh"
If the line above did not print a "checkpoint armed" confirmation, either the plugin root did not resolve OR CLAUDE_CODE_SESSION_ID was not exported into the inline step - in that case run the arm script yourself now with the Bash tool, where CLAUDE_CODE_SESSION_ID is present: it lives at ${CLAUDE_PLUGIN_ROOT}/tools/baton-checkpoint-now.sh (the pass-the-baton plugin install directory). Then write the checkpoint progress file for this session, following the standard checkpoint protocol the hook injects on your next tool action. Prepare the handoff first; do not continue unrelated work.
Invoking this command is the decision to hand off. Write the progress file, then do what /clear does: end this session so a new one starts. Do not ask the user whether they would rather keep working - they answered that by running the command. See docs/context-baton.md § Checkpoint Modes, case 1B.
Known gap until the mode fix lands: the post-write hook still emits a "Keep working in this session, or clear now?" prompt on this path. That prompt is the superseded trigger-based split, not the intended behavior.
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.
- 8d ago First seen · 15 lines · 22 tokens per session scan A ebe966278fc3
renew is a command published in the GitHub repository AaronCarney/pass-the-baton (2 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 301 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-08-31.
Other commands, from other repositories
remember
Stores decisions, patterns, and outcomes in the MCP memory knowledge graph as entities with typed observations and relations. Supports recording architectural decisions, anti-patterns, tool preferences, workflow outcomes, and project conventions that persist across sessions. Use when saving patterns, remembering…
memory
Unified read-side memory operations including knowledge graph search, session context loading, decision timeline viewing, and Mermaid graph visualization. Subcommands: search, load, history, viz, status. Complements /ork:remember (write-side). Use when searching past decisions, loading context, or visualizing the…
recall
Recall memories with filtering and search.
query
Structured frontmatter queries using yq.
search
Full-text search across all memories.
learn
Distill a finished conversation into classified knowledge candidates and propose (never auto-apply) memory writes or a new-skill hand-off. Closes the loop between a completed agent chain and the persistent memory system.