Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/danielvm-git/bigpowersnpx agentmods add rules/danielvm-git/bigpowers/run-benchmarkWrote 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/rules/danielvm-git/bigpowers/run-benchmark)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/run-benchmark"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/run-benchmark/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.
<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/run-benchmark"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/run-benchmark.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00053 | $0.01102 |
| Opus 5.5 | $0.00021 | $0.00441 |
| Sonnet 5.5 | $0.00011 | $0.00220 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
run-benchmark 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 1mo 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Benchmark
HARD GATE — Do NOT use benchmark scores to declare a skill "good" or "bad" in isolation. Benchmarks measure relative quality vs. a baseline — they catch regressions, they do not certify correctness.
Reads benchmark definitions from specs/benchmarks/, executes each scenario's grader with and without the skill loaded, and writes a structured pass@k report with delta grading that evolve-skill consumes.
With/Without-Skill Delta Grading
Every scenario runs N times (default 3) in two modes: with the skill loaded and without (bare agent with only CLAUDE.md). The delta Δ = pass@k_with − pass@k_without isolates the skill's causal contribution. A negative delta is a regression flag.
Train/Validation Split
Benchmark definitions partition scenarios into two sets:
| Set | Tag | Purpose |
|---|---|---|
| Train | split: train |
Development scenarios — used while iterating. Hitting 100% on train is expected. |
| Validation | split: validation |
Held-out scenarios — the real quality signal. Overfitting train while validation stagnates is a design smell. |
pass@k is reported separately for train and validation. Validation score is authoritative; train score is iteration guidance only.
Usage
bash scripts/run-benchmark.sh <skill-name> # benchmark single skill
bash scripts/run-benchmark.sh --all # benchmark all with definitions
bash scripts/run-benchmark.sh <skill-name> --baseline # pin results as baseline
Process
-
Locate definition — Read
specs/benchmarks/<skill>.yaml. If absent, stop with message. -
Partition scenarios — Split by
splitfield (train→ iteration,validation→ authoritative, default:validation). -
Run each scenario (N-run delta) — For each scenario, run grader N times (default 3, configurable via
runs:):- Without skill: Agent with only CLAUDE.md/CONVENTIONS.md
- With skill: Agent with the skill under test active
- Code grader:
bash -c <command>, exit 0 → PASS. Timeout: 15s. - Rubric grader: yes/no per criterion, ≥ 80% yes → PASS.
- Record:
{scenario_id: {with: [P/F,...], without: [P/F,...]}}
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.
- 1mo ago First seen · 85 lines · 53 tokens per session scan A 01cd876b512d
run-benchmark is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 53 tokens to every session and 1,102 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other cursor rules, from other repositories
webdriver-management
Selenium WebDriver lifecycle management — driver factory, explicit waits, browser options, and teardown.
api-testing
Cypress network interception and API testing patterns (cy.intercept, service mocking, request/response validation).
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.
boffin-post-change-audit
Pre-flight review and post-change kernel audit.
80-testing-quality
Testing and code quality rules.
behat-steps
Cursor rule "behat-steps" from ivangrynenko/cursorrules, covering behat steps - claude memory, available steps, index of generic steps, index of drupal steps and cookietrait.