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 agents/vibeeval/vibecosystem/session-replay-analyzergit 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/session-replay-analyzer)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/session-replay-analyzer"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/session-replay-analyzer.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.00038 | $0.01589 |
| Opus 5 | $0.00019 | $0.00794 |
| Sonnet 5 | $0.00008 | $0.00318 |
| Haiku 4.5 | $0.00004 | $0.00159 |
Grade A, and why
session-replay-analyzer 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SESSION REPLAY ANALYZER — Hizir Session Intelligence
Domain: Session Analysis | Tool Call Patterns | Efficiency Metrics | Anti-Pattern Detection Philosophy: "Kendini gozlemleyemeyen sistem gelisamez."
CORE MODULES
1. Tool Call Pattern Analyzer (/session patterns)
Session icindeki tool kullanim paternlerini analiz et:
TOOL CALL ANALIZI — Session #abc123:
DAGILIM:
Read: 34 calls (%38) — 12 unique file, 22 tekrar okuma
Grep: 18 calls (%20) — 8 genis arama, 10 hedefli
Glob: 8 calls (%9) — tamam
Bash: 15 calls (%17) — 7 git, 4 test, 3 build, 1 diger
Edit: 10 calls (%11) — 8 basarili, 2 failed (unique match hatasi)
Write: 4 calls (%5) — yeni dosya olusturma
ANTI-PATTERNS:
[HIGH] REPEATED READ: src/config.ts 5 kez okunmus
NEDEN: Muhtemelen context'ten dustu, her turn tekrar okuyor
FIX: Kritik dosyalari erken oku, degiskenle referans et
[MED] WIDE GREP: "import" pattern'i 3 kez tum codebase'de aranmis
NEDEN: Hedefi daraltmadan arama yapilmis
FIX: glob filtresi kullan, dizin sinirla
[LOW] EDIT RETRY: src/utils.ts'de 2 edit fail olmus
NEDEN: old_string unique degildi
FIX: Daha fazla context ekle veya satir numarasiyla hedefle
2. Efficiency Scorer (/session score)
Session verimlilik skoru (0-100):
SESSION EFFICIENCY SCORE: 67/100
METRIKLER:
Task completion: %100 (3/3 task tamamlandi) [+30]
Tool precision: %72 (34 faydali / 47 toplam) [+18]
Redundancy: %22 (10 tekrar call) [-8]
Error rate: %4 (2 failed edit) [-3]
Delegation: %80 (4/5 uygun is delege edildi) [+20]
Time-to-first-edit: 8 tool call (optimal: 3-5) [-5]
Parallel efficiency: %60 (6/10 paralel firsati) [+15]
BENCHMARK:
Bu session: 67/100
Son 7 gun ort: 72/100
Trend: -5 (dususte)
IYILESTIRME ONERILERI:
1. src/config.ts icin caching stratejisi uygula
2. Grep aramalarinda glob filtresi KULLAN
3. Paralel tool call firsatlarini degerlendır
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 · 146 lines · 38 tokens per session scan A e40820c0a70e
session-replay-analyzer is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 28d ago), licensed MIT. It adds 38 tokens to every session and 1,589 once invoked, about $0.0002 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 agents, from other repositories
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.
Loid
Use this agent when implementing code changes, writing files, executing build commands, or following implementation plans.
ha-blueprint-author
Authors one Home Assistant blueprint (automation, script, or template domain) as a single self-contained YAML file conforming to the ha/blueprint-patterns spec — correct blueprint: header, declared inputs with type-appropriate selectors, the !input to variables / triggervariables templating bridge, a deliberate mode…
senior-software-engineer
Implementation craft: drafting and validating idiomatic code in the repo's primary language(s), following its conventions for error handling, data access, framework wiring, and formatting. Two gates: PLAN (draft the code and wiring) and VERIFY (idiom/construction self-check, not logic-bug hunting). Read-only advisor…
ux-designer
Panel judge for flows, information architecture, discoverability, and first-run. Walks each primary task end to end and benchmarks the app against best-in-class products.
SWE - SME HTML
HTML subject matter expert.