arbe-benchmark-agent-guidance

Benchmarks agent guidance changes by comparing fresh-agent runs across controlled A/B trials.

Updated May 16, 2026
One-click install
npx skills add https://github.com/oskarrough/robots --skill arbe-benchmark-agent-guidance-oskarrough
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arbe-benchmark-agent-guidance
Source: https://github.com/oskarrough/robots/tree/main/skills/benchmark-agent-guidance
Command: npx skills add https://github.com/oskarrough/robots --skill arbe-benchmark-agent-guidance-oskarrough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing a skill, AGENTS.md, or system prompt often feels like an improvement but there is no proof. This Skill turns guidance changes into controlled experiments: pin the task, change one variable, run fresh agents before and after, and compare tokens, tool calls, failures, and correctness so you keep only changes that measurably help. ## Core Features & Use Cases - Controlled A/B methodology: Freeze prompt bytes, product revision, model, reasoning level, auth, and backend state so only the tested axis varies between runs. - Structured evidence capture: Record wall time, input/output/reasoning/cache tokens, model tool calls, surface actions, failed actions, retries, outcome, and cleanup per trial in a defined metrics table. - Decision framework: Rank results by correctness first, then policy compliance, cleanup, failures, wall time, tool calls, and tokens, with a standard report format. - Use Case: You rewrote a routing section in AGENTS.md. Run three fresh-agent trials of the same read-only task before and after the edit, then compare failed actions and input tokens to decide whether to keep the change. ## Quick Start Ask the agent to benchmark whether a recent edit to AGENTS.md reduced tool calls and tokens by running the same fixed prompt with fresh agents before and after the change.

Frequently Asked Questions about arbe-benchmark-agent-guidance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test whether an AGENTS.md change actually helped?▼

Run the exact same prompt with fresh agent sessions before and after the edit, keeping model, reasoning level, and environment fixed. Compare correctness first, then failed actions, wall time, tool calls, and tokens across at least three trials per side.

How to benchmark LLM agents without contaminating results?▼

Use a fresh agent session for every cell so prior tools, answers, and loaded files cannot leak in. Freeze prompt bytes, product revision, auth profile, backend fixtures, and harness configuration, changing only the one axis under test.

What metrics should I record when benchmarking agent guidance?▼

Record wall time, input/output/reasoning/cache tokens, model tool calls, surface actions, failed actions, retries, outcome, and cleanup per trial. Count behavioral failures like wrong routes or 404 snapshots even when commands exit zero.

Can I compare models and reasoning levels with the same benchmark?▼

Yes, treat provider, model ID, or reasoning level as the single changed axis while keeping prompts and environment identical. Validate the runtime's actual model first, since a silently substituted model invalidates the cell.

How many trials are needed for a reliable agent benchmark?▼

One run per cell is enough for an exploratory pass to find large mistakes. For a decision, run at least three trials per cell and report median plus range, and never claim statistical significance from a tiny sample.

When is parallel execution of benchmark runs invalid?▼

Run cells sequentially when they share a browser daemon, auth profile, mutable backend, rate limit, terminal, or dev server. Parallel execution is only valid for fully isolated resources, otherwise contention skews timing and state.