agent-eval

Benchmarks coding agents' performance via reproducible YAML-defined tasks and git worktrees.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Maelwalser/claude-config --skill agent-eval-maelwalser
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-eval
Source: https://github.com/Maelwalser/claude-config/tree/main/skills/agent-eval
Command: npx skills add https://github.com/Maelwalser/claude-config --skill agent-eval-maelwalser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematizes head-to-head comparisons of coding agents by running reproducible tasks, isolating runs, and measuring pass rate, cost, time, and consistency so teams can choose agents based on data rather than impressions.

Core Features & Use Cases

  • Declarative task definitions using YAML to specify repo commit, files, prompts, and judge criteria.
  • Isolated execution via git worktrees and commit pinning to prevent cross-run interference and ensure reproducibility.
  • Multi-metric benchmarking that captures pass/fail, API cost, wall-clock time, and consistency across repeated runs; supports pytest, shell commands, grep/pattern checks, and LLM-based judges.
  • Use case: run 3 trials of multiple agents against representative tasks to determine the best candidate for CI integration or team adoption.

Quick Start

Run agent-eval against a task YAML and two agents to produce a comparison report.

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 with reproducible benchmarks?▼

You can compare coding agents by running reproducible benchmarks using declarative task YAML definitions that specify repository commits, prompts, and judge criteria to measure pass rate, cost, time, and consistency.

How do I run isolated benchmarks to prevent cross-run interference when testing coding agents?▼

Run isolated benchmarks using git worktrees and commit pinning to prevent cross-run interference, ensuring that each agent evaluation remains completely reproducible and independent from other test runs.

What metrics can I measure when evaluating coding agents on coding tasks?▼

Evaluating coding agents captures multi-run metrics including pass or fail status, API cost, wall-clock time, and consistency across repeated trials to provide a complete performance comparison.

Can I use pytest and shell commands as deterministic judges for agent evaluation?▼

Yes, agent evaluation supports deterministic judges including pytest, shell commands, grep pattern checks, and LLM-based judges to verify coding agent task completion accurately.

Does agent-eval work with local repositories for head-to-head agent comparison?▼

Yes, agent evaluation applies to agent comparison scenarios across local repositories, using task YAML definitions and git worktrees to isolate runs and ensure reproducible results.

What is the best way to choose a coding agent for CI integration based on data?▼

Run multiple trials of different agents against representative tasks using reproducible benchmarks, then aggregate multi-run metrics like pass rate and cost to choose agents based on data rather than impressions.