bench

Run OhMyCode coding benchmarks and record pass-fail outcomes with token usage.

131|4|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill bench-alphalab-ustc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bench
Source: https://github.com/AlphaLab-USTC/OhMyCode/tree/main/.claude/skills/bench
Command: npx skills add https://github.com/AlphaLab-USTC/OhMyCode --skill bench-alphalab-ustc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you measure how well a provider or model performs on realistic coding tasks, with token tracking and repeatable results.

Core Features & Use Cases

  • End-to-end benchmarking: Runs a fixed suite of SWE-bench-style coding tasks through OhMyCode.
  • Model comparison: Lets you compare different providers, models, or endpoints with the same workload.
  • Performance analysis: Captures pass/fail outcomes, token usage, and runtime so you can identify regressions or efficiency gains.
  • Closed-loop debugging: Helps distinguish model limitations from OhMyCode bugs after failures.

Quick Start

Run the benchmark with your current configuration by asking to benchmark OhMyCode and then review the generated scorecard and results file.

Frequently Asked Questions about bench

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run coding benchmarks to compare different model providers?

Coding benchmarks compare model providers by running a fixed suite of SWE-bench-style tasks through OhMyCode. You can configure different providers and endpoints to execute the same workload and review the generated scorecard for pass-fail outcomes and token usage.

What is regression testing for coding models and when do I need it?

Regression testing for coding models identifies performance drops or efficiency gains after configuration changes. You need it when evaluating models or debugging failures, using benchmark scorecards to capture pass-fail outcomes, token usage, and runtime to distinguish model limitations from system bugs.

Does the benchmark harness support configurable providers and task filters?

Yes, the benchmark harness supports configurable providers, models, and task filters. It requires this configurability to execute SWE-bench-style coding tasks and output machine-readable result files for accurate model evaluation and provider comparison.

How do I track token usage during model evaluation on coding tasks?

Track token usage during model evaluation by running SWE-bench-style coding tasks through the benchmark harness. It records pass-fail outcomes alongside token consumption and runtime, generating a scorecard to analyze efficiency gains or regressions across different providers.

Can I use benchmark scorecards for closed-loop debugging?

Yes, you can use benchmark scorecards for closed-loop debugging. By analyzing pass-fail outcomes, token tracking, and runtime data from SWE-bench-style tasks, you can distinguish between model limitations and OhMyCode system bugs after task failures.