google/benchmark is a C++ library for measuring the performance of small code sections, much like tests measure correctness. Developers use it to run repeatable microbenchmarks and compare execution results.
Borrowing it
Nothing to install: this file belongs to google/benchmark. 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/google/benchmark/main/AGENTS.mdgit clone --depth 1 https://github.com/google/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/instructions/google/benchmark/agents-md)<a href="https://agentmods.dev/instructions/google/benchmark/agents-md"><img src="https://agentmods.dev/badge/instructions/google/benchmark/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/google/benchmark/agents-md"><img src="https://agentmods.dev/badge/instructions/google/benchmark/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.00410 | $0.00410 |
| Opus 5.5 | $0.00164 | $0.00164 |
| Sonnet 5.5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
benchmark 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.
What it actually says
AI usage
[!NOTE] The modern (as of 2026-06) AI is a misnomer,
- it is not conscious / not a consciousness,
- it is not sentient,
- it is not intelligent,
- it does not think,
- it does not understand the code,
- it is merely a next-token guesser,
... therefore it is merely an (hyper-) advanced IDE.
[!NOTE] A contribution is any externally-observable interaction with a project.
[!CAUTION] Failure to follow the following rules may result in repercussions, possibly without a prior warning.
Rules:
- It is acceptable to use AI when producing contributions.
[!WARNING] Any and all AI usage MUST be fully and explicitly disclosed in every contribution.
- All contributions shall be done by conscious, sentient beings. Fully autonomous contributions by bots are prohibited1.
[!WARNING] Dear contributor, the AI is your tool, and its output is for your consumption. It is your responsibility to consume said output, interpret it, and then produce the contribution itself. DO NOT just query it and post the output, especially so for all non-code contributions!
- The contributor (conscious, sentient being) solely bears the whole responsibility for the contribution, they must understand the problem, and the solution, and be able to constructively argue about it. "well, AI said so, therefore it is" is not an acceptable approach.
Footnotes
-
Unless explicitly allowed by maintainers on case-by-case basis before the contribution is submitted, in which case the bot owner (conscious, sentient being) is recognized as the de facto contributor. E.g. https://github.com/apps/dependabot is allowed. ↩
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 · 45 lines · 410 tokens per session scan A b6065ae9c491
benchmark AGENTS.md is an instructions file published in the GitHub repository google/benchmark (10,500 stars, last pushed yesterday), licensed Apache-2.0. It adds 410 tokens to every session, about $0.0016 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.
benchmark AGENTS.md compared with instructions from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| benchmark AGENTS.mdgoogle/benchmark | Instructions file | 11k | yesterday | Apache-2.0 | A | 410 | Codex, OpenCode |
| vscode buildNext.instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 9,719 | GitHub Copilot |
| next.js AGENTS.mdvercel/next.js | Instructions file | 143k | today | MIT | A | 7,461 | Codex, OpenCode |
| vscode oss-third-party-notices.instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 5,516 | GitHub Copilot |
| langchain AGENTS.mdlangchain-ai/langchain | Instructions file | 149k | today | MIT | A | 4,680 | Codex, OpenCode |
| vscode copilot-instructions.mdmicrosoft/vscode | Instructions file | 195k | today | MIT | A | 3,093 | GitHub Copilot |
| deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness | Instructions file | 274k | 2d ago | MIT | A | 4,313 | Codex, OpenCode |