openbench: Instructions file for Claude Code

CLAUDE.md

openbench CLAUDE.md is an instructions file for Claude Code from groq/openbench. It costs 1,099 tokens per session, scanned A, original, MIT.

Repository instructions for OpenBench, a Python project for running and developing benchmarks, which are repeatable tests used to compare systems. They cover virtual-environment setup, dependency management with UV, tests, code checks, and the command-line interface.

In plain words
What is it for?
They help create the environment, install dependencies, run unit and integration tests, check formatting and types, run pre-commit checks, and list available benchmarks.
Why use it?
They provide the project's required setup and quality rules, helping developers avoid using the wrong package manager or running commands outside the expected environment.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is groq/openbench's own configuration. It tells Claude Code how to work on openbench itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything openbench configures →

Reuse

Borrowing it

Nothing to install: this file belongs to groq/openbench. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/groq/openbench/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/groq/openbench

Made for: Claude Code.

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 openbench CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/groq/openbench/claude-md/github.svg)](https://agentmods.dev/instructions/groq/openbench/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/groq/openbench/claude-md"><img src="https://agentmods.dev/badge/instructions/groq/openbench/claude-md/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 openbench CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/groq/openbench/claude-md"><img src="https://agentmods.dev/badge/instructions/groq/openbench/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,099 This file is loaded in full into every session.
When invoked 1,099 The same file — it is already loaded in full.
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.01099 $0.01099
Opus 5.5 $0.00440 $0.00440
Sonnet 5.5 $0.00220 $0.00220
Haiku 4.5 $0.00110 $0.00110

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

Security

Grade A, and why

openbench CLAUDE.md 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 2mo 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.

CLAUDE.md · 148 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Essential Setup

  • Always source the virtual environment before running Python commands: source .venv/bin/activate
  • This project uses UV as the package manager, not pip
  • Dependency management: When adding dependencies with UV, use >= constraints (e.g., uv add "package>=1.2.3")
    • Exception: inspect-ai must remain pinned to a specific version for stability
    • Use the latest stable version as the minimum to keep dependencies healthy and secure
    • Check latest versions with uv pip list --outdated or on PyPI

Key Commands

Development Setup

# Initial setup
uv venv && uv sync --dev
source .venv/bin/activate

Running Tests

# Run all unit tests
pytest

# Run integration tests (requires API keys)
pytest -m integration

# Run specific test file
pytest tests/test_registry.py

# Run with coverage
pytest --cov=openbench

Code Quality

# Format code
ruff format .

# Lint code
ruff check .

# Type checking
mypy .

# Run all pre-commit hooks
pre-commit run --all-files

Using the CLI

# List available benchmarks
bench list

# Describe a specific benchmark
bench describe mmlu

# Run evaluation
bench eval mmlu --model groq/llama-3.1-70b --limit 10

# View previous results
bench view

Installing Dependencies

# Install core dependencies only (runs most benchmarks)
uv sync

# Install with specific benchmark dependencies
uv sync --group scicode       # For SciCode benchmark
uv sync --group jsonschemabench # For JSONSchemaBench

# Install with development tools
uv sync --dev

# Install everything
uv sync --all-groups

Publishing to PyPI

# Build the package
uv build

# Publish to PyPI (requires PyPI API token)
uv publish

Architecture Overview

Project Structure

  • src/openbench/ - Main package directory
    • _cli/ - CLI commands implementation
    • datasets/ - Dataset loaders (MMLU, GPQA, HumanEval, SimpleQA)
    • evals/ - Benchmark implementations built on Inspect AI
    • metrics/ - Custom scoring metrics
    • scorers/ - Scoring functions used across benchmarks
    • utils/ - Shared utilities
    • _registry.py - Dynamic task loading system
    • config.py - Benchmark metadata and configuration

Read the full file on GitHub · 148 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. 2mo ago First seen · 148 lines · 1,099 tokens per session scan A 68f9fb2a0ef8

Subscribe to this mod's changes

openbench CLAUDE.md is an instructions file published in the GitHub repository groq/openbench (831 stars, last pushed 10d ago), licensed MIT. It adds 1,099 tokens to every session, about $0.0044 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-08-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens