agent-eval

Compare coding agents on YAML-defined repository tasks and report pass rate, cost, time, and consistency metrics.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/riftzen-bit/gemini-setup --skill agent-eval-riftzen-bit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-eval
Source: https://github.com/riftzen-bit/gemini-setup/tree/main/skills/agent-eval
Command: npx skills add https://github.com/riftzen-bit/gemini-setup --skill agent-eval-riftzen-bit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable, measurable way to compare coding agents on real repository tasks so teams can choose the best model based on data rather than intuition.

Core Features & Use Cases

  • Declarative task definitions: Define tasks, judges, and pinned commits in YAML for reproducible experiments.
  • Isolated agent runs: Create per-run git worktrees so agents cannot interfere with each other or the base repository.
  • Rich metrics and reporting: Collect pass rate, cost, wall-clock time, and cross-run consistency to produce side-by-side comparison reports.
  • Use Case: Run three trials of gemini-code and aider against a unit-test-backed task to pick the most reliable, cost-effective agent for a CI pipeline.

Quick Start

Run agent-eval against your task YAML and agent list to produce a reproducible comparison report showing pass rate, cost, time, and consistency.

Frequently Asked Questions about agent-eval

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

FAQPage Schema
How do I compare coding agents on reproducible repository tasks?

Compare coding agents on reproducible tasks by defining YAML task definitions, evaluating them in isolated git worktrees, and reporting pass rate, cost, time, and consistency metrics. This approach ensures agents do not interfere with each other or the base repository during evaluation.

What is the best way to benchmark LLM coding agents using unit tests?

Benchmark LLM coding agents by running multiple trials against unit-test-backed tasks using deterministic judges like pytest. The evaluation collects structured metrics including pass rate, wall-clock time, and cost to produce a side-by-side comparison report.

Can I use an LLM judge alongside deterministic pytest checks for agent evaluation?

Yes, agent evaluation supports deterministic judges such as pytest and command executions, pattern-based checks using grep, and optional LLM judging to verify task completion. These judges collect structured metrics for each run to ensure comprehensive evaluation.

How do you ensure coding agents do not interfere with each other during benchmark runs?

Prevent interference during benchmark runs by creating per-run isolated git worktrees for each agent. Combined with pinned commits in YAML task definitions, this guarantees reproducible experiments without agents modifying the base repository.

Does agent benchmarking work with pinned commits for reproducible experiments?

Yes, reproducible experiments are achieved by defining tasks and pinned commits in YAML task definitions. By applying these definitions to isolated git worktrees across multiple runs per agent, the benchmark yields consistent and comparable metrics.