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 agentmods add commands/mrzeszowski/claude-code-keep-alive/ongit clone --depth 1 https://github.com/mrzeszowski/claude-code-keep-aliveWrote 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/mrzeszowski/claude-code-keep-alive/on)<a href="https://agentmods.dev/commands/mrzeszowski/claude-code-keep-alive/on"><img src="https://agentmods.dev/badge/commands/mrzeszowski/claude-code-keep-alive/on.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 | $0.00013 | $0.00086 |
| Opus 5 | $0.00006 | $0.00043 |
| Sonnet 5 | $0.00003 | $0.00017 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
on 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 3d 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
Run keep-alive on $ARGUMENTS using the Bash tool and print its stdout/stderr
verbatim, with no commentary, no summarization, and no follow-up suggestions.
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.
- 3d ago First seen · 9 lines · 13 tokens per session scan A d0f7efa36145
on is a command published in the GitHub repository mrzeszowski/claude-code-keep-alive (1 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 86 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
README
Git workflow and quality assurance commands for the claude-skills repository.
notebook
Low-ceremony capture for ideas (half-formed, want to mature into stories), todos (concrete actions), and notes (durable project/team facts for future recall). One-line capture, conditional elaboration AUQ. Use BEFORE thoughts get forced into stories.
sync
Manually sync current session to GitHub now.
statusline
Configure which sections appear in the Claude Code statusline.
ccc-checkpoint
Create or verify a workflow checkpoint — git commit, state snapshot, and safety gate before proceeding.
ccc-compound
Post-task learning capture — extract patterns, corrections, and decisions to compound productivity.