agent-eval

Compares coding agents head-to-head on YAML-defined tasks with pass rate, cost, and time metrics.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill agent-eval-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-eval
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/agent-eval
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill agent-eval-freedom909

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 vibe-based comparisons with reproducible benchmarks that measure pass rate, cost, time, and consistency on your own codebase tasks. ## Core Features & Use Cases - Declarative Task Definitions: Define evaluation tasks in YAML with prompts, target files, pinned commits, and judge criteria (pytest, grep, or LLM-as-judge). - Git Worktree Isolation: Each agent 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 3-5 tasks representing your real workload, run each agent 3 times per task, and use the report to make a data-backed selection decision. ## Quick Start Ask the agent to define a YAML evaluation task for your repository and run agent-eval to compare Claude Code and Aider across three runs, then generate 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 like Claude Code and Aider?▼

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

How to benchmark AI coding agents on my own codebase?▼

Create a tasks directory with YAML definitions pointing at your repository and pin a specific commit for reproducibility. Use deterministic judges like pytest or build commands alongside grep patterns to verify the agent's output.

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 so agents cannot interfere with each other or corrupt the base repository.

What judge types can verify coding agent output?▼

Three judge types are supported: code-based judges running pytest or arbitrary commands, pattern-based grep judges checking for specific code patterns, and LLM-as-judge prompts for semantic evaluation. Including at least one deterministic judge per task is recommended.

How many runs are needed for reliable agent comparison?▼

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