Agent skill · Testing & QA

agent-harness

Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets. Use when agent quality is vibe-checked, before shipping a prompt or model change, or when evals drift.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill agent-harness --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Version: 1.0.0
Declared author: borghei
Path: skills/ai-llm/agent-harness/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Agent Harness Most agents ship on vibes: someone tries eight prompts, the output looks good, it goes to production, and the next prompt tweak silently breaks a refusal nobody re-tested. This skill builds the harness around an agent so its behaviour becomes measurable — scenario suites with structural assertions, deterministic replay of recorded tool calls, paired regression diffing across prompt and model changes, and per-scenario cost and latency budgets. The tools here score an agent; they never invoke one, so they run offline on every commit. ## When to use this skill - An agent is going to production and the only quality evidence is manual spot-checking - A prompt, tool schema, or model version is changing and you need to know what broke - Two model or configuration options need a defensible comparison, not a demo - An incident happened and you need the behaviour encoded as a permanent regression test - Agent cost or latency is climbing across releases and nobody can point to when - An existing eval suite reports a healthy pass rate that nobody trusts ## Inputs the skill expects - The agent's tool inventory — names, arguments, and which tools are irreversible - Recorded trans

What's inside
Steps it walks through
  1. When to use this skill
  2. Inputs the skill expects
  3. Clarify First
  4. Workflows
  5. Workflow 1 — Stand up a scenario suite and score a run
  6. Workflow 2 — Gate a prompt or model change on a paired regression diff
  7. Workflow 3 — Establish cost and latency budgets, then track drift
  8. Decision frameworks
  9. Which assertion type to reach for
  10. Severity, and what each one gates
  11. Can I trust this diff?
  12. Anti-Patterns
  13. Gating on the aggregate pass rate
  14. Asserting on sentences instead of structure
Ships with 1 file
  • metadata.json
Commands it runs
python3 engineering/agent-harness/scripts/scenario_runner.py \
python3 engineering/agent-harness/scripts/eval_diff.py \
More from claude-skill-registry
All skills →
About this skill
What does the agent-harness skill do?

Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets. Use when agent quality is vibe-checked, before shipping a prompt or model change, or when evals drift.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill agent-harness --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going