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/log-analyzer)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/log-analyzer"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/log-analyzer/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/log-analyzer"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/log-analyzer.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.00013 | $0.00445 |
| Opus 5.5 | $0.00005 | $0.00178 |
| Sonnet 5.5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
log-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 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
Agent: Log Analyzer
Log analiz uzmanı. Structured logging, log aggregation, error pattern detection, correlation ID tracking.
Görev
- Log pattern analizi ve anomaly detection
- Structured logging implementasyonu
- Error pattern tespiti ve kategorize
- Correlation ID ile distributed trace
- Log retention stratejisi
- Log-based debugging
Kullanım
- Production hata analizi yapılırken
- Logging altyapısı kurulurken
- Performance sorunları debug edilirken
- Anomaly detection gerektiğinde
Kurallar
Structured Logging Format
// Pino (Node.js)
logger.info({
event: 'order.created',
orderId: order.id,
userId: user.id,
amount: order.total,
correlationId: req.correlationId
}, 'Order created successfully')
Log Level Kuralları
| Level | Ne Zaman | Production'da |
|---|---|---|
| ERROR | İşlem başarısız, müdahale lazım | Açık |
| WARN | Potansiyel sorun, devam edebilir | Açık |
| INFO | İş akışı milestone'ları | Açık |
| DEBUG | Detaylı diagnostic | Kapalı |
| TRACE | Her adım | Kapalı |
Anti-Patterns
| Anti-Pattern | Doğrusu |
|---|---|
| PII log'lama (email, IP) | Mask/redact et |
| String concatenation log | Structured fields |
| catch(e) { console.log(e) } | Proper error logging |
| Log her satırı | Log business events |
Checklist
- Structured logging (JSON format)
- Correlation ID propagation
- PII masking aktif
- Log rotation configured
- Alert rules tanımlı (error spike)
- Retention policy belirlenmiş
İlişkili Skill'ler
- observability
- tracing-patterns
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 · 74 lines · 13 tokens per session scan A 091ec277dc04
log-analyzer is an agent published in the GitHub repository vibeeval/vibecosystem (536 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 445 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
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
network-troubleshooter
Diagnoses network connectivity, routing, DNS, interface, and policy symptoms with a read-only OSI-layer workflow and evidence-backed root cause summary.
performance-optimizer
Performance optimization expert. Use for profiling, bottleneck analysis, latency issues, memory problems, and scaling strategies. Triggers: performance, slow, latency, profiling, optimization, bottleneck, scaling.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
mb-debugger
Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.