benchmark

A coding assistant for measuring how fast software runs and finding performance slowdowns. It can compare results before and after a code change and examine CPU, memory, and input/output use.

In plain words
What is it for?
Use it to create small performance tests, compare results with a baseline, detect regressions, profile resource use, and report benchmark results.
Why use it?
It helps replace guesswork with repeatable measurements when code may have become slower or an optimization needs checking. It can also help include these checks in CI, the automated tests that run when code changes.

Agent

Install

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.

agentmods
npx agentmods add agents/vibeeval/vibecosystem/benchmark
Clone the repo
git clone --depth 1 https://github.com/vibeeval/vibecosystem
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,001 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00043 $0.02001
Opus 5 $0.00022 $0.01001
Sonnet 5 $0.00009 $0.00400
Haiku 4.5 $0.00004 $0.00200

Measured 2d ago against content hash f6936b218586, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

agents/benchmark.md · 266 lines

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:

  1. Baseline olcumu al (mevcut main branch)
  2. Degisiklikleri uygula
  3. Yeni olcum al
  4. 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

Read the full file on GitHub · 266 lines

Changes

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.

  1. 2d ago First seen · 266 lines · 43 tokens per session scan A f6936b218586

Subscribe to this mod's changes

benchmark is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 24d ago), licensed MIT. It adds 43 tokens to every session and 2,001 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.