benchmark-models

Solid

Cross-model benchmark. Runs one prompt or skill through Claude, GPT (Codex CLI), and Gemini side by side and compares latency, tokens, cost, tool calls, and optionally output quality via an Anthropic-API judge. Answers "which model is actually best for this skill?" with data. Use when you say "benchmark models", "compare models", "which model is best for X", "cross-model comparison", or "model shootout". Do NOT use to measure web page performance.

AI & Automation 38 stars 13 forks Updated today MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
53
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# benchmark-models Run the same prompt across providers and compare them on data, not vibes. The deterministic work lives in `scripts/model_benchmark.py` (stdlib-only, ported from gstack's bun benchmark; no SDKs, no gstack runtime). This skill is the interactive wrapper: pick a prompt, preview auth with a dry-run, confirm providers, run, interpret, optionally save. Providers wrap existing CLIs and their own auth (no API keys needed except the optional judge): - `claude` via `claude -p --output-format json` - `gpt` via `codex exec ... -s read-only --json` - `gemini` via `gemini -p ... --output-format stream-json` ## Triggers Invoke this skill when the user says any of: - `benchmark models` - `compare models` - `model shootout` - `which model is best` - `cross-model comparison` Do NOT invoke for web page performance (that is a different concern). ## Preconditions - At least one provider CLI installed and authenticated. The Step 1 dry-run reports exactly which are ready; if none are, the skill stops. - The optional quality judge needs `ANTHROPIC_API_KEY` (adds ~$0.05/run). ## Process Resolve the driver first. In a repository checkout, use `BENCH="$(git rev-parse --show-toplevel)/.claude/skills/benchmark-models/scripts/model_benchmark.py"`. From an installed skill copy, use the local skill path: `BENCH="$PWD/scripts/model_benchmark.py"` when your shell is in the `benchmark-models` skill directory. ### Step 1: Pick a prompt and preview auth (dry-run) Decide the prom...

Details

Author
rjmurillo
Repository
rjmurillo/ai-agents
Created
7 months ago
Last Updated
today
Language
Markdown
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

benchmark-models

Cross-model benchmark for vibestack skills. Runs the same prompt through Claude, GPT (via Codex CLI), and Gemini side-by-side — compares latency, tokens, cost, and optionally quality via LLM judge. Answers "which model is actually best for this skill?" with data instead of vibes.

5 Updated 1 weeks ago
timurgaleev
AI & Automation Listed

benchmark-models

Cross-model benchmark for gstack skills. Runs the same prompt through Claude, GPT (via Codex CLI), and Gemini side-by-side — compares latency, tokens, cost, and optionally quality via LLM judge. Answers "which model is actually best for this skill?" with data instead of vibes. Separate from /benchmark, which measures web page performance. Use when: "benchmark models", "compare models", "which model is best for X", "cross-model comparison", "model shootout". (gstack) Voice triggers (speech-to-text aliases): "compare models", "model shootout", "which model is best".

0 Updated today
Tekkiiiii
AI & Automation Listed

benchmark-opencode-models

Deep-benchmark which OpenCode models are actually viable for opencode-bridge — ping each candidate model, then run 5 canned superpowers-style task prompts per model (feature vs bugfix, short vs detailed, plus a dedicated TDD red-to-green prompt), independently verify every result by executing the generated code (never trust OpenCode's self-reported "done"), and score each run on time/quality/completeness/autonomy/discipline/red-green-accuracy/test-call-discipline. For a fast pass/fail availability check with no scoring, use check-opencode-models instead.

0 Updated 5 days ago
darkstar1227