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/snooze)<a href="https://agentmods.dev/commands/aaroncarney/pass-the-baton/snooze"><img src="https://agentmods.dev/badge/commands/aaroncarney/pass-the-baton/snooze.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.00017 | $0.00164 |
| Opus 5 | $0.00009 | $0.00082 |
| Sonnet 5 | $0.00003 | $0.00033 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
snooze 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
Snooze checkpointing for this session:
!bash "${CLAUDE_PLUGIN_ROOT}/tools/baton-snooze.sh" $ARGUMENTS
If the line above did not print a "snoozed" 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 snooze script yourself now with the Bash tool (where CLAUDE_CODE_SESSION_ID is present), passing the same optional minutes argument: it lives at ${CLAUDE_PLUGIN_ROOT}/tools/baton-snooze.sh. Then tell the user how long checkpointing is deferred.
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 · 12 lines · 17 tokens per session scan A 9f9f290f534a
snooze is a command published in the GitHub repository AaronCarney/pass-the-baton (2 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 164 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
skill-refresh
You are running inside a headless Claude Code session in the neo4j-skills repository. Goal: scan Neo4j release notes and deprecation pages, then update any SKILL.md and references/ files that are stale, outdated, or missing new features. Open no PRs or commits — output only file edits. The workflow will handle git and…
brand-setup
Configure a new brand profile with colors, fonts, logo, visual style, platforms, and compliance rules.
screens
Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
reset
Guided teardown of an organic-os site - what gets deregistered automatically, what you must delete or revoke yourself, and why.