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.
npx agentmods add instructions/groq/openbench/claude-mdgit clone --depth 1 https://github.com/groq/openbenchWhat 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 | $0.01099 | $0.01099 |
| Opus 5 | $0.00549 | $0.00549 |
| Sonnet 5 | $0.00220 | $0.00220 |
| Haiku 4.5 | $0.00110 | $0.00110 |
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 3d 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 — 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-aimust 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 --outdatedor on PyPI
- Exception:
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 implementationdatasets/- Dataset loaders (MMLU, GPQA, HumanEval, SimpleQA)evals/- Benchmark implementations built on Inspect AImetrics/- Custom scoring metricsscorers/- Scoring functions used across benchmarksutils/- Shared utilities_registry.py- Dynamic task loading systemconfig.py- Benchmark metadata and configuration
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.
- 3d ago First seen · 148 lines · 1,099 tokens per session scan A 68f9fb2a0ef8
openbench CLAUDE.md is an instructions file published in the GitHub repository groq/openbench (813 stars, last pushed 7d ago), licensed MIT. It adds 1,099 tokens to every session, about $0.0055 per session on Opus 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.
Other instructions, from other repositories
postfix copilot-instructions.md
Instructions for sous-chefs/postfix, covering copilot instructions for sous chefs cookbooks, repository overview, project structure, build and test system and environment setup.
agentkit CLAUDE.md
Instructions for worldcoin/agentkit, covering claude.md, project overview, dev commands, install dependencies and build the library.
postfix AGENTS.md
Instructions for sous-chefs/postfix: This cookbook manages Postfix through operating system packages and service/configuration files. It does not build Postfix from source.
varnish AGENTS.md
Instructions for sous-chefs/varnish, covering agents.md, agent guidance, package availability, apt (debian/ubuntu) and dnf/yum (rhel family).
ossec AGENTS.md
Instructions for sous-chefs/ossec, covering agents.md, cookbook purpose, agent findings, known limitations and package availability.
nfs AGENTS.md
Instructions for sous-chefs/nfs, covering agent notes, package availability, apt (debian/ubuntu), dnf/yum (rhel family, fedora, amazon linux) and zypper (suse).