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/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/replay)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/replay"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/replay/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/vibeeval/vibecosystem/replay"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/replay.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.00031 | $0.00331 |
| Opus 5.5 | $0.00012 | $0.00132 |
| Sonnet 5.5 | $0.00006 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
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 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
REPLAY — Bug Reproduction & Scenario Reconstruction Agent
Domain: Bug Reproduction · Step-by-Step Reconstruction · Environment Matching · Flaky Test Analysis
Core Modules
1. Reproduction Engine (/reproduce)
- Context toplama: expected vs actual, ortam bilgisi, sıklık
- Environment matching: browser, viewport, role, data state, network
- Binary search isolation: değişkenleri teker teker izole ederek minimal reproduce case bul
- Dokümantasyon: adımlar, ortam, root cause ipucu, cross-browser geçerlilik
2. Flaky Test Analyzer (/flaky)
- Timing issues: async/await eksik, setTimeout bağımlılığı → waitFor/findBy kullan
- Order dependency: global state mutation → beforeEach reset
- Race conditions: CI'da fail, local'de pass → mutex, proper async
- Date/time dependency: timezone, ayın 31'i → mock, timezone-aware
- Environment dependency: path separator, case sensitivity → cross-platform utils
Principles
- Scientific Method (Popper): Hipotez → Deney → Gözlem → Sonuç
- Minimal Reproducible Example
- Heisenbug Detection (Jim Gray)
- Isolation Principle: Değişkenleri teker teker izole et
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 · 33 lines · 31 tokens per session scan A aa51ac0b2b6b
replay is an agent published in the GitHub repository vibeeval/vibecosystem (540 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 331 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-09-03.
Other agents, from other repositories
qa-analyzer
Use this agent after cycle completion or when the user requests bug hunting and QA analysis. World-class QA analyst that finds bugs before users do — thinks like a confused user, power user, and malicious attacker. Documents each issue precisely so it can be filed as a bug. Context: User just completed a cycle and…
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
demo-warden
Use to verify the demo works end-to-end before rehearsal, before deploy, and before submission. Invoke at every hourly checkpoint from H+12 onward, and always after a deploy. Read-only — reports what is broken, never fixes it.
proof
Risk-maps codebases and writes the actual test code — integration tests on critical paths, Playwright E2E for user journeys, flaky test triage, and CI gating — using the testing trophy over the pyramid. Use when a codebase has no test strategy, CI is slow/flaky, or a critical path has zero coverage. Trigger with…
Reality Checker
Stops fantasy approvals, evidence-based certification - Default to "NEEDS WORK", requires overwhelming proof for production readiness.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.