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 instructions/constripacity/claude-replay/claude-mdgit clone --depth 1 https://github.com/constripacity/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/instructions/constripacity/claude-replay/claude-md)<a href="https://agentmods.dev/instructions/constripacity/claude-replay/claude-md"><img src="https://agentmods.dev/badge/instructions/constripacity/claude-replay/claude-md.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.00810 | $0.00810 |
| Opus 5 | $0.00405 | $0.00405 |
| Sonnet 5 | $0.00162 | $0.00162 |
| Haiku 4.5 | $0.00081 | $0.00081 |
Grade A, and why
Claude-Replay CLAUDE.md 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 4d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Replay — context for Claude Code
What this repo is
Observability layer for Claude Code sessions — the cross-project search / analytics / visualization that complements native resume/rewind (it does NOT re-implement them; see the positioning note below). Hooks silently into every session, stores events + checkpoints in SQLite, exposes 10 MCP tools. Sibling to Claude Bridge under Constripacity.
Positioning (load-bearing — read before adding features)
Native Claude Code already does resume (--continue/--resume), rewind
(/rewind), and plaintext /export. Replay must NOT duplicate those. Build only
in the differentiated lane: full-text search, per-session analytics
(metrics.py / classify.py), session diff, and visualization (dashboard/TUI/
structured export). Filter every new feature through "does native already do this?"
Architecture in one sentence
Passive hooks write to SQLite. MCP tools read from SQLite. Dashboard + TUI visualize SQLite. Nothing else.
Port
8766 (Bridge is 8765 — deliberately different)
Key files
- claude_replay/store.py — all DB access lives here, nowhere else
- claude_replay/hooks.py — hook handlers, dispatched by
claude-replay hook <type> - claude_replay/resume.py — resume brief generation (death cause + live git state)
- claude_replay/classify.py — death-cause classification (pure, no DB access)
- claude_replay/metrics.py — per-session insight metrics (pure, no DB access)
- claude_replay/doctor.py —
doctorself-check (pure evaluate(); CLI gathers facts) - claude_replay/analytics.py — cross-session rollup (pure aggregate(), no DB access)
- claude_replay/export.py — trace rendering (html / json / md)
- claude_replay/server.py — Starlette app (MCP SSE + JSON API + static)
- claude_replay/tui_client.py — async httpx client over the JSON API (testable, no Textual)
- claude_replay/tui.py — Textual session browser (talks to a running
serve, never the DB) - claude_replay/cli.py — all CLI subcommands
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.
- 4d ago First seen · 67 lines · 810 tokens per session scan A 290dbccba147
Claude-Replay CLAUDE.md is an instructions file published in the GitHub repository constripacity/Claude-Replay (1 stars, last pushed 12d ago), licensed MIT. It adds 810 tokens to every session, about $0.0040 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.