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/arbazkhan971/godmode/benchnpx skills add arbazkhan971/godmode --skill benchgit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/bench)<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>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 | $0.00066 | $0.02073 |
| Opus 5 | $0.00033 | $0.01037 |
| Sonnet 5 | $0.00013 | $0.00415 |
| Haiku 4.5 | $0.00007 | $0.00207 |
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.
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
optimizefor that.benchmeasures, 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 declaresdirection).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 undoprep(default:git checkout -for refs,unset VARfor env)
baseline— name of the variant all deltas are computed against. Must match onevariants[].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
- Validate inputs —
metric_cmdmust emit a single number;baselinemust match a variant;N >= 3. - Snapshot starting git state (
HEADsha, branch, dirty bit). Refuse to run if working tree is dirty. - FOR each variant in order:
a. Run
prep. Abort variant on non-zero exit, markprep_failed. b. Runmetric_cmdN 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 variantmeasurement_error, record best-effort numbers. f. Runteardown. Fail loud if teardown leaves repo dirty. - Restore starting git state exactly (same sha, same branch). Verify with
git rev-parse HEAD. - Compute
delta_pctfor each variant vs. baseline:(variant.median - baseline.median) / baseline.median * 100. - Emit outputs (see Output Format).
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.
- 5d ago First seen · 150 lines · 66 tokens per session scan A ca9b1fa8780f
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.
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…
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.
codex
Run benchmark-selected GPT-5.6 work through the Codex CLI.
agent-code-generator
Generates Agent definitions (.md files) based on user intent and standard templates.
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…
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.