agent-eval

Compares coding agents on YAML-defined tasks using git worktree isolation and pass-rate metrics.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Femad-6/my-skills --skill agent-eval-femad-6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-eval
Source: https://github.com/Femad-6/my-skills/tree/main/.github/skills/agent-eval
Command: npx skills add https://github.com/Femad-6/my-skills --skill agent-eval-femad-6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing between coding agents like Claude Code, Aider, or Codex usually relies on anecdotal impressions rather than data. This Skill replaces guesswork with reproducible head-to-head benchmarks that measure pass rate, cost, time, and consistency on your own real tasks. ## Core Features & Use Cases - Declarative Task Definitions: Define benchmark tasks in YAML with prompts, target files, pinned commits, and judge criteria (pytest, grep patterns, or LLM-as-judge). - Isolated Agent Runs: Each run executes in a fresh git worktree, so agents cannot interfere with each other or corrupt the base repository. - Comparison Reports: Generate tabular reports comparing agents across pass rate, API cost, wall-clock time, and consistency over repeated runs. - Use Case: Before adopting a new coding agent for your team, define five tasks representative of your workload, run each agent three times per task, and select the winner based on measured pass rate and cost. ## Quick Start Ask the agent to define a YAML benchmark task for your repository and run a head-to-head comparison of two coding agents with three runs each.

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 like Claude Code and Aider?

Define tasks in YAML files specifying the prompt, target files, and judge criteria, then run each agent multiple times with the agent-eval CLI. The report command produces a table comparing pass rate, cost, time, and consistency.

How do I write a benchmark task for a coding agent?

Create a YAML file with a name, description, repo path, target files, a prompt describing the change, and judge rules such as pytest commands or grep patterns. Pin a specific commit so results stay reproducible over time.

Does agent-eval require Docker for isolation?

No, agent-eval uses git worktrees instead of Docker. Each agent run gets a fresh worktree created from the pinned commit, providing isolation without container overhead.

How many runs are needed for reliable agent comparison?

Run at least three trials per agent per task because coding agents are non-deterministic. Consistency is measured as pass rate across repeated runs, such as 3 out of 3 passes equaling 100 percent.

What judge types can validate agent output?

Three judge types are supported: deterministic code-based judges like pytest or build commands, pattern-based grep checks on files, and LLM-as-judge prompts. Include at least one deterministic judge per task since LLM judges add noise.