run-evals

run-evals is a cursor rule for Cursor from danielvm-git/bigpowers. It costs 49 tokens per session (817 once invoked), scanned A, original, MIT.

An evaluation workflow for defining tests before building a new agent capability or feature. It supports runnable checks and written pass/fail rubrics, then records results across repeated attempts.

In plain words
What is it for?
It is for writing capability and regression evaluations, assigning their strictness, running them, and blocking release when required checks fail.
Why use it?
It makes success measurable before implementation and helps catch regressions—new failures caused by later changes.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit It is for writing capability and regression evaluations, assigning their strictness, running them, and blocking release when required checks fail.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/danielvm-git/bigpowers/run-evals
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.

Clone the repo
git clone --depth 1 https://github.com/danielvm-git/bigpowers

Made for: Cursor.

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 run-evals

README.md
[![agentmods](https://agentmods.dev/badge/rules/danielvm-git/bigpowers/run-evals/github.svg)](https://agentmods.dev/rules/danielvm-git/bigpowers/run-evals)
Your own site
<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/run-evals"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/run-evals/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.

agentmods 80×15 button for run-evals

Your own site · 80×15
<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/run-evals"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/run-evals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 817 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00049 $0.00817
Opus 5.5 $0.00020 $0.00327
Sonnet 5.5 $0.00010 $0.00163
Haiku 4.5 $0.00005 $0.00082

Measured 1mo ago against content hash e386365f5370, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

run-evals 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.

.cursor/rules/run-evals.mdc · 80 lines

How it starts

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

Run Evals

HARD GATE — Define evals before implementation. Code graders = runnable verify: commands; model graders = explicit rubric with pass/fail criteria.

Process

  1. Name the capability under test (one sentence).

  2. Write specs/EVALS-<feature>.md with:

    • Capability evals (does it do the job?)
    • Regression evals (did we break anything?)
  3. Assign grader type per eval: code (shell verify) or model (rubric).

  4. Assign strictness tier per eval (graduated promotion — e45s37):

    Tier Meaning Promotion rule
    EXPERIMENTAL New eval, may flake Not gating
    USUALLY_PASSES Stable in dev; ≥2/3 recent runs pass Blocks BUILD only when combined with ALWAYS_PASSES suite
    ALWAYS_PASSES Zero tolerance; required for release Any single failure blocks BUILD and merge

    Promote: EXPERIMENTAL → USUALLY_PASSES after 3 consecutive passes; USUALLY_PASSES → ALWAYS_PASSES after 5 consecutive passes with zero flakes documented in specs/state.yaml.

  5. Run evals; log results table with pass@k (e.g. 3/3 runs) and tier per eval.

  6. Block BUILD phase until all ALWAYS_PASSES evals pass at agreed k. USUALLY_PASSES failures warn; EXPERIMENTAL failures log only.

Artefact

specs/verifications/eNNsYY-eval-report.md — see REFERENCE.md for template. Eval reports are stored alongside verification evidence in specs/verifications/, keyed by story ID for traceability.

Verify

→ verify: test -d specs/benchmarks && test -f specs/benchmarks/SCHEMA.md


Run Evals — Reference

Strictness tiers (e45s37)

Add a tier: column to each eval row:

Tier Gate behaviour
EXPERIMENTAL Log only — does not block
USUALLY_PASSES Warn on failure; blocks only when paired with failing ALWAYS_PASSES
ALWAYS_PASSES Hard block on any failure

EVALS template

# EVALS: <feature>

## Capability
| ID | Eval | Grader | Tier | verify / rubric |
|----|------|--------|------|-----------------|
| C1 | ... | code | ALWAYS_PASSES | `verify: npm test -- <file>` |
| C2 | ... | model | USUALLY_PASSES | Rubric: [ ] criterion A [ ] criterion B |

## Regression
| ID | Eval | Grader | verify / rubric |
|----|------|--------|-----------------|
| R1 | Full suite passes | code | `verify: npm test` |

## Results
| Run | C1 | C2 | R1 | pass@k |
|-----|----|----|-----|--------|
| 1 | PASS | PASS | PASS | 3/3 |

Read the full file on GitHub · 80 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. 1mo ago First seen · 80 lines · 49 tokens per session scan A e386365f5370

Subscribe to this mod's changes

run-evals is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 49 tokens to every session and 817 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.