eval-harness

eval-harness is a skill for Claude Code from hamzaPixl/pixl-ai. It costs 62 tokens per session (927 once invoked), scanned A, original, MIT.

A test harness for measuring how well skills, agents, and prompts work across repeated test cases.

In plain words
What is it for?
Use it to run capability or regression evaluations, calculate pass-at-k results, and generate evaluation reports.
Why use it?
It makes it easier to detect regressions, where a later change causes previously working behavior to fail, and to compare capability results.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the pixl-crew plugin — 93 skills, 14 agents, 6 hooks shipped together

Good fit Use it to run capability or regression evaluations, calculate pass-at-k results, and generate evaluation reports.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hamzapixl/pixl-ai/eval-harness
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add hamzaPixl/pixl-ai --skill eval-harness
Clone the repo
git clone --depth 1 https://github.com/hamzaPixl/pixl-ai

Made for: Claude Code.

Or install pixl-crew, the plugin that ships this one along with the rest of its 93 skills, 14 agents, 6 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for eval-harness

README.md
[![agentmods](https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/eval-harness/github.svg)](https://agentmods.dev/skills/hamzapixl/pixl-ai/eval-harness)
Your own site
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/eval-harness"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/eval-harness/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for eval-harness

Your own site · 80×15
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/eval-harness"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/eval-harness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 927 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.00927
Opus 5 $0.00031 $0.00464
Sonnet 5 $0.00012 $0.00185
Haiku 4.5 $0.00006 $0.00093

Measured 10d ago against content hash 62d09303e209, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

eval-harness scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/crew/skills/eval-harness/SKILL.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Eval Harness

Structured evaluation framework for measuring skill, agent, and prompt quality.

Step 0: Parse Arguments

  • target — skill name, agent name, or path to a prompt file
  • --k=N — number of runs per test case (default: 3)
  • --modecapability (can it do X?) or regression (did it break?)

Step 1: Discover Test Cases

For Skills

  1. Read the skill's SKILL.md for expected behavior
  2. Check for existing eval files: skills/<name>/evals/ or skills/<name>/test-cases.jsonl
  3. If none exist, generate test cases from the skill description

For Agents

  1. Read the agent's .md file for trigger examples and role
  2. Extract test scenarios from <example> blocks
  3. Generate edge cases from role constraints

For Prompts

  1. Read the prompt file
  2. Extract expected outputs from comments or paired .expected files

Step 2: Define Evaluation Criteria

Each test case needs:

{
  "input": "the prompt or task",
  "criteria": [
    {"name": "correctness", "type": "binary", "description": "Does it produce the right output?"},
    {"name": "format", "type": "binary", "description": "Does it follow the expected format?"},
    {"name": "completeness", "type": "scale_1_5", "description": "Are all required elements present?"}
  ],
  "blockers": ["must not hallucinate file paths", "must not modify excluded files"]
}

Step 3: Run Evaluations

For each test case, run k times:

  1. Execute the skill/agent/prompt
  2. Capture the full output
  3. Evaluate against criteria (use a judge prompt if automated checking isn't possible)
  4. Record pass/fail per criterion

Step 4: Calculate Metrics

Metric Formula
pass@1 % of test cases passing on first try
pass@k % passing at least once in k runs
precision Correct outputs / total outputs
recall Required elements present / total required

Read the full file on GitHub · 109 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 109 lines · 62 tokens per session scan A 62d09303e209

Subscribe to this mod's changes

eval-harness is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 927 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens