evals-run

evals-run is a command for Claude Code from HoangNguyen0403/agent-skills-standard. It costs 0 tokens per session (791 once invoked), scanned A, original, MIT.

A command for running blinded live evaluations that measure whether an agent skill changes behaviour using isolated, outcome-based evidence.

In plain words
What is it for?
Use it to start or resume evaluation runs, create selective baselines, reuse compatible evidence, and publish reproducible results.
Why use it?
It provides a repeatable way to compare agent results without letting prior answers or mutable context distort the evaluation.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to start or resume evaluation runs, create selective baselines, reuse compatible evidence, and publish reproducible results.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hoangnguyen0403/agent-skills-standard/evals-run
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.

Clone the repo
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

Made for: Claude Code.

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 evals-run

README.md
[![agentmods](https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/evals-run/github.svg)](https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/evals-run)
Your own site
<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/evals-run"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/evals-run/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 evals-run

Your own site · 80×15
<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/evals-run"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/evals-run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 791 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.00000 $0.00791
Opus 5 $0.00000 $0.00396
Sonnet 5 $0.00000 $0.00158
Haiku 4.5 $0.00000 $0.00079

Measured 9d ago against content hash 20e01434c1a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

evals-run 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 9d 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.

.claude/commands/evals-run.md · 69 lines

How it starts

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

Evals Run

Input: $ARGUMENTS

Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

Execute the following steps for $ARGUMENTS.

description: Run blinded live skill evals and publish reproducible v2 results.

Goal

Measure whether a skill changes agent behavior with isolated, immutable, outcome-based eval evidence.

Steps

1. Choose or resume a run

  • For ordinary maintenance after a complete catalog baseline exists, run pnpm evals:baseline first. It creates or resumes a selective manifest, reuses only compatible evidence, and prints the model, reasoning level, concurrency, and fresh-answer count without starting workers.

  • Review that plan before spending quota. Start workers only with pnpm evals:baseline -- --execute; the default is gpt-5.6-luna with high reasoning and one worker. Override intentionally with EVALS_MODEL, EVALS_REASONING_EFFORT, or EVALS_CONCURRENCY (maximum four workers).

  • If usage is exhausted, keep the run directory and rerun the identical --execute command after access resumes; completed answers are reused automatically.

  • Use pnpm evals:manifest -- --category <category> for one category or pnpm evals:manifest -- --all for the complete catalog.

  • Use pnpm evals:manifest -- --resume <runId> only when deliberately continuing an existing run; a new invocation always creates a collision-safe run ID.

  • Record the printed run ID. The manifest records source hashes, the v2 schema, and the generation protocol.

2. Answer each blinded case

  • Run each baseline and with-skill arm in a separate worker/context.
  • Baseline receives only the prompt. With-skill receives the same prompt plus that skill's SKILL.md.
  • Trigger cases receive only the skill name and one-line description; never open the full skill body or expose the expected label.
  • Trigger prompt filenames use opaque case IDs; never infer the expected label from filenames or ordering.
  • For all runs, write answers under answers/<category>/<skill>/<case>; category runs use answers/<skill>/<case>.
  • Mark known compromised baselines in the manifest and do not use them for delta calculations until clean reruns replace them.

Read the full file on GitHub · 69 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. 9d ago First seen · 69 lines · 0 tokens per session scan A 20e01434c1a5

Subscribe to this mod's changes

evals-run is a command published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 791 tokens. 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-09-03.