agent-benchmark: Instructions file for Codex

AGENTS.md

agent-benchmark AGENTS.md is an instructions file for Codex, OpenCode from bence-toth/agent-benchmark. It costs 989 tokens per session, scanned A, original, MIT.

Project instructions for agent-benchmark, a Node.js command-line tool that runs the same coding task in separate Git worktrees and compares the results. A worktree is an additional working copy of a Git repository, and the comparison includes reports and cost metrics.

In plain words
What is it for?
They are for working on agent-benchmark's command parsing, configuration, metrics, pricing, reports, reviews, and tests.
Why use it?
They give the coding agent the project structure, constraints, and testing expectations it needs to change the tool safely.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is bence-toth/agent-benchmark's own configuration. It tells Codex and OpenCode how to work on agent-benchmark itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-benchmark configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bence-toth/agent-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.

Copy the file
curl -O https://raw.githubusercontent.com/bence-toth/agent-benchmark/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/bence-toth/agent-benchmark

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for agent-benchmark AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/bence-toth/agent-benchmark/agents-md/github.svg)](https://agentmods.dev/instructions/bence-toth/agent-benchmark/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/bence-toth/agent-benchmark/agents-md"><img src="https://agentmods.dev/badge/instructions/bence-toth/agent-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.

agentmods 80×15 button for agent-benchmark AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/bence-toth/agent-benchmark/agents-md"><img src="https://agentmods.dev/badge/instructions/bence-toth/agent-benchmark/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 989 This file is loaded in full into every session.
When invoked 989 The same file — it is already loaded in full.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00989 $0.00989
Opus 5.5 $0.00396 $0.00396
Sonnet 5.5 $0.00198 $0.00198
Haiku 4.5 $0.00099 $0.00099

Measured 2mo ago against content hash 6b41f48c16cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-benchmark AGENTS.md scanned grade A 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- **Minimal dependencies.** Only `js-yaml` is a runtime dependency. Everything else uses Node.js built-ins (`fs/promises`, `child_process`, `path`, `readline`, `node:test`).
AGENTS.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent instructions for agent-benchmark

Project overview

agent-benchmark is a Node.js CLI tool (ESM, no build step) that runs a coding task across multiple git worktrees – each with different AI assistant config files – and produces a comparison report. It is published to npm as agent-benchmark.

The entry point is bin/cli.js. All logic lives in lib/. Tests are flat in test/ (no subdirectories).

Architecture

bin/cli.js              – subcommand router
lib/
  args.js               – flag parsing (parseInitArgs, parseRunArgs, parseReviewArgs, parseCopilotReviewArgs)
  config.js             – YAML load + validate (loadConfig)
  copilot-reviewer.js   – GitHub Copilot review orchestration (runCopilotReview)
  init.js               – agent-benchmark init (initBenchmark)
  metrics.js            – stream-json parsing (parseMetrics, createCollector)
  pricing.js            – cost normalization accounting for cache pricing (normalizedCost)
  report.js             – table render + file write (generateReport, writeResultFiles, listResults, showResult, resolveTimestamp, loadResultSet)
  review-prompt.js      – review prompt construction (buildReviewPrompt)
  review-report.js      – review report render + file write (printReviewReport, writeReviewFiles)
  reviewer.js           – Claude-based review orchestration (runReview)
  runner.js             – Claude process orchestration (runBenchmark)
  worktree.js           – git worktree lifecycle (worktreePath, branchName, createWorktree, applyConfigOverlay, commitChanges, discardChanges, removeWorktree, pushBranch, getBaseCommit, getDiffStats)
  commands/
    copilot-review.js   – copilot-review subcommand
    init.js             – init subcommand
    results.js          – results subcommand
    review.js           – review subcommand
    run.js              – run subcommand

Key constraints

  • ESM only. All files use import/export. No require(). No .mjs extensions needed because "type": "module" is set in package.json.
  • No build step. Source runs directly. Do not add transpilation.
  • Minimal dependencies. Only js-yaml is a runtime dependency. Everything else uses Node.js built-ins (fs/promises, child_process, path, readline, node:test).
  • Node 18+ only. Use the built-in test runner (node:test), fs/promises, Array.findLast, and other Node 18 APIs freely.

Read the full file on GitHub · 79 lines

Changes

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.

  1. 2mo ago First seen · 79 lines · 989 tokens per session scan A 6b41f48c16cc

Subscribe to this mod's changes

agent-benchmark AGENTS.md is an instructions file published in the GitHub repository bence-toth/agent-benchmark (2 stars, last pushed 5mo ago), licensed MIT. It adds 989 tokens to every session, about $0.0040 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,750 tokens

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.

denoland/deno · 3,077 tokens