Borrowing it
Nothing to install: this file belongs to TaimoorKhan10/replayd. 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/TaimoorKhan10/replayd/main/AGENTS.mdgit clone --depth 1 https://github.com/TaimoorKhan10/replaydWrote 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/taimoorkhan10/replayd/agents-md)<a href="https://agentmods.dev/instructions/taimoorkhan10/replayd/agents-md"><img src="https://agentmods.dev/badge/instructions/taimoorkhan10/replayd/agents-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.1 | $0.04501 | $0.04501 |
| Opus 5 | $0.02250 | $0.02250 |
| Sonnet 5 | $0.00900 | $0.00900 |
| Haiku 4.5 | $0.00450 | $0.00450 |
Grade A, and why
replayd AGENTS.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 8d 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 — 551 lines — stays where its author put it; the contents beside it link to each section on GitHub.
replayd — Three Agent Examples
Turn failed AI agent runs into replayable regression tests.
This document covers the three example agents in the examples/ directory and explains how each one demonstrates the replayd release-control loop.
Table of Contents
- What replayd does
- The four-step loop
- Agent integration contract
- Example 1 — Multi-step Planning Agent
- Example 2 — RAG Policy Agent
- Example 3 — Production Incident Response Agent
- Running everything
- Test results
- Grading reference
What replayd does
AI agents regress silently. A team fixes a bug, ships a new prompt or model, and the same bad behavior quietly returns. Traditional software has regression tests and CI/CD to catch this. AI agents have had nothing equivalent.
replayd is the fix. It captures a failed agent run in full — input, output, every tool call — marks it as a known failure, saves it as a regression test, and then replays that test against every future version of the agent before you ship.
capture → mark_failed → save_test → replay_all
If the same bad behavior returns, the release is blocked. That is the entire idea.
The four-step loop
from replayd import Replayd
rp = Replayd()
# 1. Capture a run
with rp.capture(input=user_input, model="gpt-4o") as run:
run.output = your_agent(user_input, run)
# 2. Mark it as failed
rp.mark_failed(run.id, reason="agent skipped constraint check")
# 3. Save as a regression test
rp.save_test(
run.id,
forbidden_actions=["finalize_plan"],
expected_action="check_constraints",
)
# 4. Replay before every future deployment
results = rp.replay_all(agent=your_agent)
for r in results:
print(r.verdict, r.reason)
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.
- 8d ago First seen · 551 lines · 4,501 tokens per session scan A c47a7e617fa5
replayd AGENTS.md is an instructions file published in the GitHub repository TaimoorKhan10/replayd (18 stars, last pushed 3mo ago), licensed MIT. It adds 4,501 tokens to every session, about $0.0225 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-30.
Other instructions, from other repositories
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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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.