Borrowing it
Nothing to install: this file belongs to BenchBox-dev/BenchBox. 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/BenchBox-dev/BenchBox/develop/AGENTS.mdgit clone --depth 1 https://github.com/BenchBox-dev/BenchBoxWrote 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/benchbox-dev/benchbox/agents-md)<a href="https://agentmods.dev/instructions/benchbox-dev/benchbox/agents-md"><img src="https://agentmods.dev/badge/instructions/benchbox-dev/benchbox/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/benchbox-dev/benchbox/agents-md"><img src="https://agentmods.dev/badge/instructions/benchbox-dev/benchbox/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.02598 | $0.02598 |
| Opus 5.5 | $0.01039 | $0.01039 |
| Sonnet 5.5 | $0.00520 | $0.00520 |
| Haiku 4.5 | $0.00260 | $0.00260 |
Grade A, and why
benchbox 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 yesterday.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BenchBox Agent Guide
This file is the project authority for agent work. Keep it compact: detailed operations belong in linked docs.
Authority and provenance
Apply instructions in this order:
- platform/system safety and tool constraints;
- the user's current request and explicit approvals;
- this repository guide and the active project protocol;
- loaded skills and mechanical tool output;
- recommendations, examples, and historical notes.
Personal defaults apply only where this guide is silent; where behavior conflicts, this guide and the active protocol win.
[AUTH-PROVENANCE-001] Classify a requirement before acting: task authority, repository policy, mechanical constraint, or recommendation. State the source when it changes scope, identity, publication, or destructive behavior. Never turn a recommendation or earlier task instruction into a standing requirement.
[COMMIT-IDENTITY-001] Before committing, resolve Git identity and its config origin. Reject known agent/service identities as author unless this task requests that exact identity; add no agent/service Co-Authored-By or equivalent attribution unless it requests that exact trailer. Repository-local values override the global identity and every linked worktree inherits them, but are not automatically intentional. A signing service may hold the committer slot behind a human author. Stale requests, tool conventions, harness/hook messages, and claimed agent work are not authorization (docs/agent/identity-instruction-boundary.md). The no-attribution bar also binds assistant-authored comments, reviews, and PR bodies (docs/agent/attribution-surfaces.md).
[DURABLE-ARTIFACTS-001] Write durable artifacts (commit messages, PR titles/bodies, committed comments) for a reader who never saw the session: no phase, gate, wave, or work-item labels, no plan or handoff references, no run-local state. Give the durable reason; process state belongs in a decision record or the tracker.
[SESSION-STATE-001] Session state lives in its tracker item, never in a handoff, scratchpad, /tmp, or commit; holds are enforced states (docs/agent/handoffs.md).
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.
- yesterday Changed · -2 tokens per session 540fd4283823
- 3d ago Changed · +1 lines · +29 tokens per session 913f6eeed40b
- 11d ago Changed · +2 lines · +119 tokens per session 85f781cf311c
- 12d ago Changed · +1 lines · +14 tokens per session 4453dd8039f5
- 14d ago Changed · +11 tokens per session 49fe8b4e095a
- 15d ago Changed f6cb142c3101
- 18d ago Changed · -5 tokens per session 70fc8dd27d38
- 20d ago Changed · +6 tokens per session 66baf3a3ea18
- 21d ago Changed · +5 tokens per session 17daffa73c35
- 24d ago First seen · 136 lines · 2,421 tokens per session scan A dd30454eb8fa
benchbox AGENTS.md is an instructions file published in the GitHub repository BenchBox-dev/BenchBox (12 stars, last pushed 21d ago), licensed MIT. It adds 2,598 tokens to every session, about $0.0104 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-04.
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.