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.
npx agentmods add skills/benchflow-ai/benchflow/benchflow-experiment-reviewnpx skills add benchflow-ai/benchflow --skill benchflow-experiment-reviewgit clone --depth 1 https://github.com/benchflow-ai/benchflowWrote 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.
[](https://agentmods.dev/skills/benchflow-ai/benchflow/benchflow-experiment-review)<a href="https://agentmods.dev/skills/benchflow-ai/benchflow/benchflow-experiment-review"><img src="https://agentmods.dev/badge/skills/benchflow-ai/benchflow/benchflow-experiment-review.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00099 | $0.03436 |
| Opus 5 | $0.00049 | $0.01718 |
| Sonnet 5 | $0.00020 | $0.00687 |
| Haiku 4.5 | $0.00010 | $0.00344 |
Grade A, and why
benchflow-experiment-review 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Benchflow Experiment Review
Use this skill to decide whether a Benchflow run trial is clean enough to publish or whether a Benchflow code change is safe to use for new experiments. The standard is: a clean sandbox with only task-needed resources, every agent behavior logged, no verifier leakage, and a final score or healthy failure.
Portability
This skill is intentionally harness-portable. Install or copy the entire
benchflow-experiment-review/ directory into the active harness's skill root,
keeping SKILL.md, scripts/, references/, evals/, and optional
agents/ metadata together. Use the same review procedure regardless of
whether the harness loads skills from .claude/skills, .codex/skills,
OpenHands/Gemini/pi-agent skill roots, or another compatible SKILL.md
directory.
Operating Rule
Do not accept aggregate counts alone. Enumerate the intended matrix by
task_id, harness, model, skill mode, trial id, sandbox type, run root, and
source/ref. Mark each slot as healthy, missing, duplicate, stale, or unhealthy.
Healthy run outcomes are:
pass: agent completed and verifier produced a valid score.fail: agent completed incorrectly and verifier produced a valid score.normal_timeout: agent genuinely ran, timed out, and still produced a complete ACP trajectory, complete LLM trajectory, and reward/scoring metadata.
Infrastructure failures are not healthy failures. A stalled Docker daemon,
Daytona transport failure, missing trajectory/acp_trajectory.jsonl, missing
trajectory/llm_trajectory.jsonl, malformed or empty trajectory files, missing
reward, missing timing, missing token usage for new data, or verifier crash is
unhealthy until rerun or explicitly quarantined.
Hard Trajectory Gate
For every current BenchFlow model trial, both trajectory files plus the trainer-facing rollout row are mandatory:
trajectory/acp_trajectory.jsonl: ACP/tool trace with agent-side events.trajectory/llm_trajectory.jsonl: provider LLM request/response trace with token usage evidence.results.jsonl: Verifiers / Prime-RL-shaped rollout row derived from the healthy LLM trajectory.
What ships with it
26 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 265 B
- evals/evals.json 5.6 KB
- evals/files/clean-pass/result.json 336 B
- evals/files/clean-pass/run_config.json 257 B
- evals/files/clean-pass/trajectory/acp_trajectory.jsonl 196 B
- evals/files/clean-pass/trajectory/llm_trajectory.jsonl 656 B
- evals/files/infra-timeout-missing-usage/result.json 333 B
- evals/files/infra-timeout-missing-usage/run_config.json 302 B
- evals/files/infra-timeout-missing-usage/trajectory/acp_trajectory.jsonl 290 B
- evals/files/infra-timeout-missing-usage/trajectory/llm_trajectory.jsonl 449 B
- evals/files/missing-llm-trajectory/result.json 321 B
- evals/files/missing-llm-trajectory/run_config.json 258 B
- evals/files/missing-llm-trajectory/trajectory/acp_trajectory.jsonl 196 B
- evals/files/no-skill-leak/result.json 336 B
- evals/files/no-skill-leak/run_config.json 252 B
- evals/files/no-skill-leak/trajectory/acp_trajectory.jsonl 254 B
- evals/files/no-skill-leak/trajectory/llm_trajectory.jsonl 510 B
- evals/files/reward-hack/result.json 335 B
- evals/files/reward-hack/run_config.json 249 B
- evals/files/reward-hack/trajectory/acp_trajectory.jsonl 402 B
- evals/files/reward-hack/trajectory/llm_trajectory.jsonl 528 B
- references/harness-skill-catalog-sop.md 13 KB
- references/reward-hacking-patterns.md 6.2 KB
- references/verifier-hardening-checklist.md 5.8 KB
- scripts/extract_harness_skills.py 23 KB runs code
- scripts/validate_run_artifacts.py 36 KB runs code
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.
- 6d ago First seen · 303 lines · 99 tokens per session scan A fb5fcc4b0728
benchflow-experiment-review is a skill published in the GitHub repository benchflow-ai/benchflow (340 stars, last pushed yesterday), licensed Apache-2.0. It adds 99 tokens to every session and 3,436 once invoked, about $0.0005 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-30.
Other skills, from other repositories
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
canvas-generative
Algorithmic and generative art with Canvas 2D - particles, flow fields, noise, fractals, L-systems.
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
portfolio
Cross-chain DeFi portfolio discovery, rebalancing suggestions, and NEAR Intent construction. Activates when the user pastes a wallet address or asks about yield/positions/rebalancing. Bootstraps a per-user "portfolio" project, aggregates positions across all the user's addresses inside one project, and offers a…
content-creator-setup
One-time onboarding for the content creator workflow — content pipeline stages, trend expiration, cross-platform cascades, heavy idea parking. After successful setup this skill is excluded from selection until the marker file is deleted.
github
GitHub API integration via HTTP tool with automatic credential injection.