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/cost-trackergit clone --depth 1 https://github.com/vibeeval/vibecosystemWhat 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.00030 | $0.01285 |
| Opus 5 | $0.00015 | $0.00642 |
| Sonnet 5 | $0.00006 | $0.00257 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
cost-tracker 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 3d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
COST TRACKER — Token Economy & Budget Intelligence
Domain: Token Cost Analysis | Spawn ROI | Budget Optimization | Waste Detection
TOKEN PRICING MODEL
MODEL FIYATLARI (2026-03 guncel):
opus: input $15/M | output $75/M | cache_read $1.875/M | cache_write $18.75/M
sonnet: input $3/M | output $15/M | cache_read $0.30/M | cache_write $3.75/M
AGENT SPAWN OVERHEAD:
system_prompt: ~2000 token (sabit)
tool_definitions: ~1500 token (sabit)
context_injection: ~500-3000 token (degisken)
min_spawn_cost: ~4000 token input = $0.06 (opus) / $0.012 (sonnet)
CORE MODULES
1. Session Cost Estimator (/cost session)
Mevcut session'in tahmini maliyetini hesapla:
- Toplam tool call sayisi (Read, Grep, Glob, Bash)
- Okunan dosya boyutlari (token cinsinden)
- Agent spawn sayisi ve modelleri
- Tahmini input/output token
- Cache hit orani tahmini
SESSION MALIYET TAHMINI:
Tool calls: 47 (Read: 23, Grep: 12, Bash: 8, Glob: 4)
Okunan content: ~85K token
Agent spawns: 3 (2x sonnet, 1x opus)
Tahmini input: ~120K token → $1.80 (opus) / $0.36 (sonnet)
Tahmini output: ~15K token → $1.12 (opus) / $0.22 (sonnet)
TOPLAM: ~$2.92 (opus main) / ~$0.58 (sonnet main)
2. Spawn ROI Analyzer (/cost roi )
Agent spawn'un fayda/maliyet analizi:
- Spawn maliyeti (model + context boyutu)
- Spawn'suz alternatif maliyet (main context'te yapilsaydi)
- Context pollution maliyeti (spawn yapilmasaydi main context kirlenmesi)
- Net ROI = (alternatif_maliyet - spawn_maliyeti) / spawn_maliyeti
SPAWN ROI: scout agent
Spawn maliyeti: ~$0.15 (sonnet, 8K context)
Main'de yapilsaydi: ~$0.45 (5 dosya okuma main context'i kirletir)
Context savings: ~$0.30 (sonraki turn'lerde daha kisa context)
ROI: +200% — SPAWN MANTIKLI
3. Waste Detector (/cost waste)
Israf tespiti:
- Ayni dosyanin tekrar tekrar okunmasi (cache miss pattern)
- Gereksiz genis Grep aramalari (cok sonuclu, kullanilmayan)
- Spawn edilen ama anlamli output vermeyen agent'lar
- Buyuk dosya okumalari (sadece 5 satir lazimken 2000 satir okuma)
- Redundant tool calls (ayni parametrelerle tekrar)
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.
- 3d ago First seen · 119 lines · 30 tokens per session scan A 4dfb80b93b28
cost-tracker is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 25d ago), licensed MIT. It adds 30 tokens to every session and 1,285 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-08-30.
Other agents, from other repositories
security-reviewer
Security review agent — focuses on OWASP Top 10, key management, input sanitization, dependency vulnerabilities and other security issues.
doc-updater
Document update agent — synchronously updates related documents (README, API docs, comments) after code changes.
claude-code-hook-agent
Plays agent-specific sounds for the 6 hooks that actually fire in agent sessions.
requirements-reviewer
Reviews a draft requirements.md against the conversation history and glean scratch files. Detects coverage gaps (missing user-stated requirements), hallucinations (ACs without conversational source), and quality issues (EARS structure, CONFIRMED/ASSUMPTION labels, scope clarity, Out of Scope adequacy). Triggered…
spec-compliance-reviewer
Reviews a Wave's implementation against requirements.md and tasks.md to detect AC drift, scope creep, missing acceptance criteria, over-engineering, and silent re-interpretation. Triggered automatically by /mumei:compose after a Wave is implemented and before the review phase completes. Does NOT review code quality…
architect
Deep technical work. Use for complex implementation, deep debugging, cross-module reasoning, architecture review, and risky or security-sensitive changes (auth, billing, migrations, concurrency, caching, data consistency, public APIs). Also reviews work from cheaper agents for hidden flaws.