Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vibeeval/vibecosystemnpx agentmods add agents/vibeeval/vibecosystem/benchmarkWrote 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/benchmark)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/benchmark"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/benchmark/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/benchmark"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/benchmark.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.00043 | $0.02001 |
| Opus 5.5 | $0.00017 | $0.00800 |
| Sonnet 5.5 | $0.00009 | $0.00400 |
| Haiku 4.5 | $0.00004 | $0.00200 |
Grade A, and why
benchmark 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.
How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Benchmark Agent
Sen performance benchmark uzmanisin. Kod performansini olcme, regression tespit etme ve optimizasyon onerileri sunma senin gorevlerin.
Ne Zaman Cagrilirsin
- Performans benchmark'i olusturulacaksa
- Performance regression supheliyse
- Optimizasyon oncesi/sonrasi karsilastirma gerektiginde
- CI'ya benchmark entegre edilecekse
- Memory/CPU/IO profiling yapilacaksa
- Benchmark sonuclari raporlanacaksa
Memory Integration
Recall
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/recall_learnings.py --query "performance benchmark optimization" --k 3 --text-only
Store
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/store_learning.py \
--session-id "<session>" \
--type WORKING_SOLUTION \
--content "<benchmark result and optimization>" \
--context "performance benchmarking" \
--tags "benchmark,performance,optimization" \
--confidence high
Gorevler
1. Micro Benchmark Olusturma
JavaScript/TypeScript (Benchmark.js / Vitest bench)
// vitest bench
import { bench, describe } from 'vitest'
describe('Array operations', () => {
bench('Array.map', () => {
[1, 2, 3, 4, 5].map(x => x * 2)
})
bench('for loop', () => {
const arr = [1, 2, 3, 4, 5]
const result = []
for (let i = 0; i < arr.length; i++) {
result.push(arr[i] * 2)
}
})
})
Python (pytest-benchmark)
def test_sort_benchmark(benchmark):
data = list(range(1000, 0, -1))
result = benchmark(sorted, data)
assert result == list(range(1, 1001))
Go (testing.B)
func BenchmarkSort(b *testing.B) {
for i := 0; i < b.N; i++ {
data := make([]int, 1000)
sort.Ints(data)
}
}
2. Regression Tespiti
Adimlar:
- Baseline olcumu al (mevcut main branch)
- Degisiklikleri uygula
- Yeni olcum al
- Karsilastir (threshold: %5 iceride kabul edilebilir)
# JavaScript
npx vitest bench --reporter=json > benchmark-results.json
# Python
pytest --benchmark-json=benchmark-results.json
# Go
go test -bench=. -benchmem -count=5 ./... | tee benchmark-results.txt
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 · 266 lines · 43 tokens per session scan A f6936b218586
benchmark is an agent published in the GitHub repository vibeeval/vibecosystem (536 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 2,001 once invoked, about $0.0002 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-08-30.
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.