bench

bench is a skill for Claude Code, Codex from arbazkhan971/godmode. It costs 66 tokens per session (2,073 once invoked), scanned A, original, MIT.

A benchmark tool for comparing a measured result across two or three code states or configurations. A benchmark is a repeated measurement used to see whether one version performs better than another.

In plain words
What is it for?
Use it for A/B comparisons, such as testing a main branch against a feature branch or comparing settings. It runs a metric command repeatedly, checks noise, and produces a TSV report and summary.
Why use it?
It makes comparisons reproducible and shows whether results vary too much to trust. It calculates changes against a chosen baseline without modifying the source code.

Skill for Claude CodeCodex

Part of the godmode plugin — 133 skills, 1 command, 9 agents, 3 MCP servers shipped together

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.

agentmods
npx agentmods add skills/arbazkhan971/godmode/bench
Any agent
npx skills add arbazkhan971/godmode --skill bench
Clone the repo
git clone --depth 1 https://github.com/arbazkhan971/godmode

Made for: Claude Code, Codex.

Or install godmode, the plugin that ships this one along with the rest of its 133 skills, 1 command, 9 agents, 3 MCP servers.

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 bench

README.md
[![agentmods](https://agentmods.dev/badge/skills/arbazkhan971/godmode/bench.svg)](https://agentmods.dev/skills/arbazkhan971/godmode/bench)
Your own site
<a href="https://agentmods.dev/skills/arbazkhan971/godmode/bench"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/bench.svg" alt="Measured on agentmods" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,073 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00066 $0.02073
Opus 5 $0.00033 $0.01037
Sonnet 5 $0.00013 $0.00415
Haiku 4.5 $0.00007 $0.00207

Measured 5d ago against content hash ca9b1fa8780f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bench 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 5d 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.

skills/bench/SKILL.md · 150 lines

How it starts

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

Activate When

  • /godmode:bench, "benchmark", "compare variants", "A/B metric"
  • User has a metric and wants a statistically-honest comparison between 2-3 code states
  • NOT for optimization loops — use optimize for that. bench measures, never modifies source.

Inputs

Ask once, cache for the session:

  • metric_cmd — shell command printing ONE number to stdout (lower-is-better or higher-is-better, user declares direction).
  • variants — list of 2-3 entries. Each variant is a record:
    • name — short label (e.g. main, terse_on, feature_branch)
    • prep — EITHER a git ref (git checkout <ref>) OR an inline shell command that puts the repo into the desired state (e.g. export GODMODE_TERSE=1, git checkout feature-branch)
    • teardown — optional shell command to undo prep (default: git checkout - for refs, unset VAR for env)
  • baseline — name of the variant all deltas are computed against. Must match one variants[].name.
  • N — runs per variant. Default 5. Minimum 3. Maximum 20.
  • variance_threshold — stdev/mean ratio that flags a variant noisy. Default 0.05 (5%).

Workflow

  1. Validate inputs — metric_cmd must emit a single number; baseline must match a variant; N >= 3.
  2. Snapshot starting git state (HEAD sha, branch, dirty bit). Refuse to run if working tree is dirty.
  3. FOR each variant in order: a. Run prep. Abort variant on non-zero exit, mark prep_failed. b. Run metric_cmd N times. Collect numbers into an array. c. Compute mean, median, stdev, cv = stdev/mean. d. IF cv > variance_threshold: retry the FULL N-run block up to 3 times (variance recovery). e. IF cv still > threshold after 3 retries: mark variant measurement_error, record best-effort numbers. f. Run teardown. Fail loud if teardown leaves repo dirty.
  4. Restore starting git state exactly (same sha, same branch). Verify with git rev-parse HEAD.
  5. Compute delta_pct for each variant vs. baseline: (variant.median - baseline.median) / baseline.median * 100.
  6. Emit outputs (see Output Format).

Read the full file on GitHub · 150 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. 5d ago First seen · 150 lines · 66 tokens per session scan A ca9b1fa8780f

Subscribe to this mod's changes

bench is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 7d ago), licensed MIT. It adds 66 tokens to every session and 2,073 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-30.

Related

Other skills, from other repositories

jobs-to-be-done

Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also…

wondelai/skills · 137 tokens

asc-subscription-localization

Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.

rorkai/app-store-connect-cli-skills · 60 tokens

codex

Run benchmark-selected GPT-5.6 work through the Codex CLI.

notque/vexjoy-agent · 18 tokens

agent-code-generator

Generates Agent definitions (.md files) based on user intent and standard templates.

majiayu000/claude-skill-registry · 20 tokens

scienceworld-growth-focuser

Use when you have planted a seed or need to track a plant's growth stage (sprouting, flowering, reproduction). Applies the 'focus on' action to a specific plant or biological entity to signal intent and monitor its development. Trigger after planting or when you need to observe life cycle progression in the…

zjunlp/SkillNet · 71 tokens

iterate-pivot-decision

Documents a strategic pivot or persevere decision with the evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.

product-on-purpose/pm-skills · 43 tokens