Borrowing it
Nothing to install: this file belongs to minghinmatthewlam/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.
curl -O https://raw.githubusercontent.com/minghinmatthewlam/openbench/main/AGENTS.mdgit clone --depth 1 https://github.com/minghinmatthewlam/openbenchWrote 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/instructions/minghinmatthewlam/openbench/agents-md)<a href="https://agentmods.dev/instructions/minghinmatthewlam/openbench/agents-md"><img src="https://agentmods.dev/badge/instructions/minghinmatthewlam/openbench/agents-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.
<a href="https://agentmods.dev/instructions/minghinmatthewlam/openbench/agents-md"><img src="https://agentmods.dev/badge/instructions/minghinmatthewlam/openbench/agents-md.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.02496 | $0.02496 |
| Opus 5.5 | $0.00998 | $0.00998 |
| Sonnet 5.5 | $0.00499 | $0.00499 |
| Haiku 4.5 | $0.00250 | $0.00250 |
Grade A, and why
openbench AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenBench — Agent Context
Read this first. It captures what this project is trying to become, so any agent
or contributor picks up the strategic context, not just the mechanics in
README.md / WRITEUP.md.
Local execution context
Before changing benchmark execution or starting a run, read agents.env when
it exists. It is a gitignored, machine-local source of truth for where code is
developed and where benchmarks are executed. Never commit it or put credentials
in it.
For this installation, code changes belong in the laptop checkout. Benchmark runs normally execute on the Mac Mini from an exact pushed commit. Do not edit source on the Mini, do not launch from a dirty or stale checkout, and check for active benchmark processes before starting another run.
What OpenBench is
A benchmark framework for comparing coding-agent harnesses (codex, pi,
opencode, cursor, devin, claude, ...) — the CLI products that wrap a model in a
run loop, tool set, and permission policy. Tasks are self-contained
(task.toml + instruction.md + Docker environment + verifier); the verifier
is the sole judge.
Execution ownership
The canonical path is obench run [suite.toml]. OpenBench compiles immutable
suite intent, stock/custom profiles, one exact Harbor job per task set, and
comparison-plan sidecars. Pinned Harbor owns task/trial execution, Docker
sandboxes, concurrency, retries, resume, locks, verifier execution, and ATIF
artifacts. OpenBench then validates/imports every intended job as one atomic
suite result, reconciles optional proxy evidence, and owns comparison,
statistics, publication policy, and site acceptance.
obench legacy run is compatibility only. Manual Harbor export, job-run, and
result-import commands remain diagnostics and migration tools; do not describe
them as the default workflow.
Product goals (the two things we are building toward)
- Community harness flywheel. Make OpenBench trivially importable and usable so third parties can add their own harnesses or harness variations and evaluate them against the stock adapters. If someone builds a better harness or feature, they should want to use OpenBench to prove it and post the results publicly — that showing-off loop is how the framework grows.
- Company/private-codebase evals. More teams evaluate agents on their own codebases and use cases rather than general benchmarks. OpenBench should be easily installable inside a private repo so companies can benchmark harnesses and models on their tasks with the same rigor (checker polarity, token metering, Wilson CIs) as the public tiers.
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.
- 2mo ago First seen · 181 lines · 2,496 tokens per session scan A dafb3b8654e9
openbench AGENTS.md is an instructions file published in the GitHub repository minghinmatthewlam/openbench (138 stars, last pushed 2mo ago), licensed MIT. It adds 2,496 tokens to every session, about $0.0100 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.
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).
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.
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).
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.
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).
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.