Borrowing it
Nothing to install: this file belongs to GoogleCloudPlatform/evalbench. 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/GoogleCloudPlatform/evalbench/main/AGENTS.mdgit clone --depth 1 https://github.com/GoogleCloudPlatform/evalbenchWrote 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/googlecloudplatform/evalbench/agents-md)<a href="https://agentmods.dev/instructions/googlecloudplatform/evalbench/agents-md"><img src="https://agentmods.dev/badge/instructions/googlecloudplatform/evalbench/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/googlecloudplatform/evalbench/agents-md"><img src="https://agentmods.dev/badge/instructions/googlecloudplatform/evalbench/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.02556 | $0.02556 |
| Opus 5.5 | $0.01022 | $0.01022 |
| Sonnet 5.5 | $0.00511 | $0.00511 |
| Haiku 4.5 | $0.00256 | $0.00256 |
Grade C, and why
evalbench AGENTS.md scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .venv/fake_home How it starts
The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EvalBench: Agentic Onboarding & Development Guide
Welcome to EvalBench! This guide is specifically designed for AI coding assistants and new developers to help you understand the repository's architecture, evaluation modes, codebase structure, and contribution flows.
Table of Contents
- Overview & Objectives
- Project Architecture
- Module Directory Layout
- Tool Paradigms & Generators
- Core Workflows & Lifecycle
- Configuration Schemas
- Local Development & Execution
- Troubleshooting & Tips
Overview & Objectives
EvalBench is a highly flexible testing and evaluation framework designed to measure the quality of Generative AI (GenAI) workflows, specifically focusing on:
- Database specific tasks: Generating valid DDL, DML, and DQL across multiple database types (AlloyDB, BigQuery, Spanner, Postgres, SQLite, etc.).
- Agent Multi-turn journeys: Simulating complex user interactions where an LLM-based simulated user responds to the agent's questions or drives the conversation via a predetermined plan.
- Extensible Scoring: Evaluating outputs with a plug-and-play suite of deterministic and LLM-based scorers.
[!NOTE] The core design principle of EvalBench is isolation. Each multi-turn execution runs in a sandboxed home directory (
.venv/fake_home/or.venv/fake_home_claude/) to prevent local machine environment contamination.
Project Architecture
EvalBench separates evaluation into distinct orchestrators, evaluators, generators, and scorers.
graph TD
Config[Run Config YAML] -->|Loads| Orch[Orchestrator]
Dataset[Dataset JSON] -->|Parsed| Orch
Orch -->|Splits scenarios by Dialect/DB| Eval[Evaluator]
subgraph Per Scenario Evaluation Loop
Eval -->|Turn 1 Prompt| Gen[Agent / Model Generator]
Gen -->|Tool Calls / Text| StepLogic{Is Multi-turn?}
StepLogic -->|Yes| VUser[Simulated User LLM]
VUser -->|Turn N Next Response| Gen
StepLogic -->|Done / Final output| Exec[SQL Execution / Scorer Work]
end
Exec -->|Store Results| Report[Reporting: CSV / BigQuery]
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 · 288 lines · 2,556 tokens per session scan C eedfa31e48cb
evalbench AGENTS.md is an instructions file published in the GitHub repository GoogleCloudPlatform/evalbench (67 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,556 tokens to every session, about $0.0102 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.