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.
git clone --depth 1 https://github.com/tanghong123/claude-replayWrote 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/tanghong123/claude-replay/jdi-handoff)<a href="https://agentmods.dev/commands/tanghong123/claude-replay/jdi-handoff"><img src="https://agentmods.dev/badge/commands/tanghong123/claude-replay/jdi-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/commands/tanghong123/claude-replay/jdi-handoff"><img src="https://agentmods.dev/badge/commands/tanghong123/claude-replay/jdi-handoff.svg" alt="Reviewed on agentmods" width="80" 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.00142 |
| Opus 5.5 | $0.00009 | $0.00057 |
| Sonnet 5.5 | $0.00004 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
jdi-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 1mo 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
Hand this interactive session over to agent-jdi so it continues unattended in the background.
Run exactly this, and nothing else:
agent-jdi handoff $ARGUMENTS
That spawns a detached watcher and quits this session; once it exits, agent-jdi resumes the same session unattended and drives the work to completion. Do not take any other actions or ask for confirmation — just run the command.
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.
- 1mo ago First seen · 18 lines · 22 tokens per session scan A ad7728dbf66a
jdi-handoff is a command published in the GitHub repository tanghong123/claude-replay (3 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 142 once invoked, about $0.0001 per session on Opus 5.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
unifly-audit
Read-only audit of UniFi WiFi security, firewall policy, and network isolation.
unifly-status
Read-only health check of UniFi infrastructure, including devices and alerts.
brain-stats
Show claudectl brain learning metrics — accuracy, correction rate, and effectiveness.
nab
Fetch, archive, or research URLs with nab.
check
Audit a .nika workflow before it runs — findings with their NIKA-XXXX codes, cost envelope, permits.
trace
Inspect a Nika run's result, trace integrity and recovery evidence.