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/sifxprime/kodelyth-ecc/replaygit clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/replay)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/replay"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/replay.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.00697 |
| Opus 5 | $0.00011 | $0.00349 |
| Sonnet 5 | $0.00004 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
replay 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/replay
Re-run a completed swarm session for regression testing, A/B comparison, or post-mortem analysis.
Quick examples
/replay swarm-2026-05-10-4a
/replay oauth-audit.bundle.json --execute
/replay swarm-2026-05-10-4a --harness codex --execute
/replay oauth-audit.bundle.json --agents security-reviewer,supply-chain-auditor --execute
/replay swarm-baseline --base-ref refactor-branch --execute
Behavior
By default, prints the dry-run plan. Add --execute to actually create worktrees, spawn the tmux session, and launch agents. The replay session is auto-named <original>-replay-<n> so it never collides with the source.
| Flag | Effect |
|---|---|
<target> |
Required. Either a bundle file path (*.json) or a session name in .orchestration/. |
--harness <h> |
Override the launcher harness (claude / codex / opencode / windsurf / echo). |
--agents a,b,c |
Replace the original agent list. |
--base-ref <ref> |
Branch base for replay worktrees (default: from bundle.meta or HEAD). |
--session <name> |
Override the auto-generated -replay-N suffix. |
--replace |
Tear down any existing session/worktrees with the same names. |
--execute |
Spawn worktrees + tmux + launch agents. |
--write-only |
Just materialize coordination files. |
--json |
Print the full plan + planConfig as JSON. |
Use cases
- Regression test prompts — capture a baseline, replay after agent rev, compare handoffs.
- Reproducible bug reports — bundle a buggy session, ship to maintainers, they can
replay --executelocally. - Model A/B test — same task, two harnesses, side-by-side handoff diff.
- Re-test against new code —
--base-ref refactor-branchre-runs the same audit on the new code. - Post-mortem — replay an incident response swarm with new agents to see what they would have caught.
Companion commands
/session-export <name>— export a coordination dir as a bundle JSON./session-import <bundle>— restore a bundle into.orchestration/.
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.
- 2d ago First seen · 62 lines · 22 tokens per session scan A 1a5c6cc8b309
replay is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 697 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-09-03.
Other commands, from other repositories
toh-help
Display all Toh Framework commands and quick usage guide.
opsx-new
Start a new change using the experimental artifact workflow (OPSX).
research
Delegate a thorough research investigation to the agy:runner subagent.
experiment
Design A/B test with statistical rigor. Usage: /mindforge:experiment [feature] [--metric conversion|engagement|revenue] [--duration 2w].
kimi-setup
Run node "$HOME/.kimi-plugin/kimi-companion.mjs" setup, then report installation and authentication status.
strategy-cfo
商业战略与财商融合决策专家 — 商业模式 / 资本结构 / 投资决策 / 资源配置 / 估值视角.