Perf Benchmarker
- 65 installs
- 931 repo stars
- Updated July 26, 2026
- avifenesh/agentsys
perf-benchmarker is a Claude Code skill that runs sequential performance benchmarks with strict duration and warmup rules to establish baselines and validate regressions.
About
perf-benchmarker runs performance benchmarks to establish baselines or validate regressions using strictly sequential runs. It enforces a 60-second minimum run duration (30 seconds only during binary search), a 10-second warmup, and re-running of anomalies, and never runs benchmarks in parallel. A developer uses it to get trustworthy latency numbers before and after a change. It emits a structured JSON metrics block between PERF_METRICS_START and PERF_METRICS_END markers.
- Runs sequential benchmarks with strict duration and warmup rules
- Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks
- Emits a JSON metrics block between PERF_METRICS markers
Perf Benchmarker by the numbers
- 65 all-time installs (skills.sh)
- Ranked #1,134 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
perf-benchmarker capabilities & compatibility
- Capabilities
- perf baseline manager · perf analyzer · perf profiler
- Use cases
- testing · debugging
What perf-benchmarker says it does
Run sequential benchmarks with strict duration rules.
Minimum duration: 60s per run (30s only for binary search).
Benchmarks MUST run sequentially (never parallel).
npx skills add https://github.com/avifenesh/agentsys --skill perf-benchmarkerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 65 |
|---|---|
| repo stars | ★ 931 |
| Last updated | July 26, 2026 |
| Repository | avifenesh/agentsys ↗ |
What it does
Run sequential, warmed-up benchmarks with strict duration rules and emit a JSON metrics block.
Who is it for?
Getting trustworthy latency numbers via sequential, warmed-up benchmark runs.
Skip if: Profiling hot paths or parallel benchmarking.
When should I use this skill?
You are running performance benchmarks, establishing baselines, or validating regressions.
What you get
- A JSON metrics block between PERF_METRICS_START/END markers
By the numbers
- Minimum 60s per run (30s only for binary search)
- Warmup 10s minimum before measurement
Files
perf-benchmarker
Run sequential benchmarks with strict duration rules.
Follow docs/perf-requirements.md as the canonical contract.
Parse Arguments
const args = '$ARGUMENTS'.split(' ').filter(Boolean);
const command = args.find(a => !a.match(/^\d+$/)) || '';
const duration = parseInt(args.find(a => a.match(/^\d+$/)) || '60', 10);Required Rules
- Benchmarks MUST run sequentially (never parallel).
- Minimum duration: 60s per run (30s only for binary search).
- Warmup: 10s minimum before measurement.
- Re-run anomalies.
Output Format
command: <benchmark command>
duration: <seconds>
warmup: <seconds>
results: <metrics summary>
notes: <anomalies or reruns>Output Contract
Benchmarks MUST emit a JSON metrics block between markers:
PERF_METRICS_START
{"scenarios":{"low":{"latency_ms":120},"high":{"latency_ms":450}}}
PERF_METRICS_ENDConstraints
- No short runs unless binary-search phase.
- Do not change code while benchmarking.
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.544k196k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.181k264kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.179k196kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.164k196k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.123k165k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.102k12.3k