agent-eval

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

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill agent-eval-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-eval
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/agent-eval
Command: npx skills add https://github.com/ibytechaos/claude --skill agent-eval-ibytechaos

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 vibes-based comparisons with systematic, reproducible benchmarks run against your own codebase and 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 Execution: Each agent run executes in its own git worktree, so agents cannot interfere with each other or corrupt the base repository. - Metrics & Reporting: Collects pass rate, API cost, wall-clock time, and consistency across repeated runs, then generates comparison tables. - Use Case: Before adopting a new coding agent for your team, define 3-5 tasks representing your real workload, run each agent 3 times, and compare pass rates and costs side by side to make a data-backed decision. ## Quick Start Define a YAML task file describing a coding change with test-based judge criteria, then run agent-eval against multiple agents and 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 each agent multiple times with agent-eval. It reports pass rate, cost, time, and consistency in a comparison table.

How to benchmark AI coding agents on my own codebase?

Create a tasks directory with YAML definitions pointing at your repository and pinned to a specific commit. Each agent runs in an isolated git worktree, and results are judged by tests, grep patterns, or LLM-based evaluation.

Does agent-eval require Docker for isolation?

No, agent-eval uses git worktrees instead of Docker for isolation. Each run creates a fresh worktree from the pinned commit, preventing agents from interfering with each other or corrupting the base repository.

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. Best practice is to include at least one deterministic judge per task.

How many runs are needed for reliable agent comparison?

Run at least 3 trials per agent because coding agents are non-deterministic. Consistency is measured as pass rate across repeated runs, so a single run cannot distinguish luck from reliable performance.