agent-evallisted

# CIEL ADAPTATION: Agent-Eval (Benchmarking Suite) This skill formalizes the process for objectively benchmarking different coding agents or underlying models against CIEL's codebase. It replaces subjective "vibes-based" comparisons with reproducible, data-driven task evaluations. ## Integration Context Adapted from `~/.agents/skills/agent-eval/`. While `eval-harness` is used to evaluate the *code output* of a specific task during active development (EDD), `agent-eval` is a meta-tool used by the Orchestrator to select or upgrade the agents themselves. ## Core Concepts ### Task Definitions Evaluations must be defined declaratively (e.g., in YAML) specifying: - The base repository and a pinned `commit` SHA (for strict reproducibility). - The target files and the specific prompt to feed the agent. - Deterministic judge commands (e.g., `npm test`, `pytest`). ### Worktree Isolation To prevent test runs from corrupting the base repository or interfering with each other, every agent evaluation run MUST execute inside an isolated Git Worktree. ## 🛡️ CRITICAL SAFETY MANDATE: Sandboxing & Isolation **Logical isolation (Git Worktrees) is NOT security isolation.** Evaluating autonomous agents involves executing arbitrary code generated by those agents. Running benchmarks directly on the host OS is strictly prohibited if the agents under evaluation have `run_shell_command` or similar capabilities. ### Mandatory Sandbox Requirements 1. **Containerization**: All evaluation tri