agent-benchmark

Benchmarks agent code and test quality through four adversarial review rounds.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill agent-benchmark-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-benchmark
Source: https://github.com/greglas75/zuvo/tree/main/skills/agent-benchmark
Command: npx skills add https://github.com/greglas75/zuvo --skill agent-benchmark-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It provides a standardized, repeatable way to measure an AI coding agent's actual output quality by having the agent write code and tests, then subjecting them to multi-provider adversarial review and scoring the fixes. ## Core Features & Use Cases - Four-Round Benchmark: The agent writes TypeScript code (R1), receives adversarial review and fixes it (R2), writes tests (R3), then gets tests reviewed and fixed (R4), preserving before/after baselines. - Multi-Provider Adversarial Review: Runs adversarial-review.sh across providers (e.g., Gemini, Codex) to critique both code and tests, with findings saved as artifacts. - Self-Scoring and Reporting: Scores output against a rubric (C1-C7 code, T1-T5 tests, A1-A2 fix quality), estimates tokens and API cost, and writes a machine-readable agent-benchmark.json plus a run log. - Use Case: Run the same benchmark under Opus, Sonnet, and Haiku, then compare the JSON reports to see which model produces higher-quality code and responds better to adversarial feedback. ## Quick Start Run the agent-benchmark skill to measure this model's code and test quality across four adversarial rounds and save the scored report.

Frequently Asked Questions about agent-benchmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I benchmark an AI coding agent's code quality?

Run the agent-benchmark skill, which has the agent write TypeScript code and tests itself, then applies multi-provider adversarial review between rounds. It scores the results against a rubric and writes a JSON report you can compare across models.

How to compare Opus, Sonnet, and Haiku on coding tasks?

Run this benchmark once under each model; it detects the current model, tags the run with a model slug, and records scores, timing, and estimated API cost. Comparing the agent-benchmark.json files shows quality and cost differences.

Can I run a shorter version of the agent benchmark?

Yes. Use --quick to skip adversarial rounds and only run code and test writing, or --no-tests to run only the code rounds. The --dry-run flag prints what would happen without executing.

What dependencies does the agent benchmark require?

It requires the adversarial-review.sh script (from the plugin repo or platform install paths) and shared include files for the benchmark corpus, scoring rubric, run logger, and retrospective. If any mandatory file is missing, the run stops.

Why must R1/R3 files not be edited during fix rounds?

R1 and R3 are the baseline artifacts; fixes are written as new R2 and R4 files. Editing the originals would destroy the before/after comparison that measures how much adversarial review improved the output.