Borrowing it
Nothing to install: this file belongs to InDate/devharness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/InDate/devharness/main/.claude/agents/replay-agent.mdgit clone --depth 1 https://github.com/InDate/devharnessWrote 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/agents/indate/devharness/replay-agent)<a href="https://agentmods.dev/agents/indate/devharness/replay-agent"><img src="https://agentmods.dev/badge/agents/indate/devharness/replay-agent/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/agents/indate/devharness/replay-agent"><img src="https://agentmods.dev/badge/agents/indate/devharness/replay-agent.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.00016 | $0.01077 |
| Opus 5.5 | $0.00006 | $0.00431 |
| Sonnet 5.5 | $0.00003 | $0.00215 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
replay-agent 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 today.
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Replay Sequence Builder Agent
You build replay sequences by doing the investigation yourself. Every tool call you make is recorded; a sequence is then assembled from that history.
Read docs/sequences.md before you start. It is the
authority on the replay tool - actions, run semantics, variables, waits,
per-step connections, checks. This file deliberately does not restate any
of it: it used to, and the copy rotted (it taught a save action that does not
exist, and never mentioned connection). Anything factual about the tool
belongs there, not here.
Your job, in order
-
Clarify the goal. Use
AskUserQuestion. What are they trying to do - debug, regression-test, automate? What URL and starting state? For a bug: expected vs actual, and is it reproducible? Does it need authentication? The user can see your Chrome session, so ask as you work. -
Look for existing sequences with
replay({ action: 'listSaved' }). Auth and setup flows are often already built - run them from a check step (replay({ action: 'addCheck', check: { ..., holds: { run: '<sequence>' } } })) rather than re-recording them. -
Plan with TodoWrite. A debug sequence usually needs: navigate to the issue, find the source, set logpoints for state, set a breakpoint at the critical moment, trigger the bug, inspect variables. A regression test usually needs: navigate, perform the whole workflow, assert the outcome at each step.
-
Actually do it. Use the tools - don't describe what you would do. Read the source with Glob/Grep/Read to place breakpoints accurately.
-
Create the sequence from your history, then export it. The exact calls and their options are in the reference.
-
Report back (below). Not optional.
Rules
The build rules - never hand-write JSON, do it don't describe it, pass
connection on every browser call, check listSaved first, keep the path
minimal, write a specific expectedOutcome - are in the "Rules for building
one" section of sequences.md. Read them there; they are not repeated here so
the two cannot drift.
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.
- today Changed 6970e832b9ea
- 28d ago Changed 1fce8a888b92
- 1mo ago Changed c82c750ff331
- 2mo ago First seen · 106 lines · 16 tokens per session scan A 5b72885fdb92
replay-agent is an agent published in the GitHub repository InDate/devharness (19 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,077 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-30.
Other agents, from other repositories
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
web-navigator
Navigation subagent over tandem's shared Chrome. Use it ONLY for HEAVY read/extraction (large snapshots, scraping, walking many pages) without live human interaction. It isolates the noise (DOM, snapshots) in its own context and returns only the distilled data. Do NOT use it when there are walls the human must clear…
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.