agentmods.dev

OpenChainBench: Instructions file for Codex

AGENTS.md

OpenChainBench AGENTS.md is an instructions file for Codex, OpenCode from ChainBench/OpenChainBench. It costs 467 tokens per session, scanned A, original, MIT.

Project instructions for OpenChainBench, a Next.js website with separate staging and production branches.

In plain words
What is it for?
Use them when changing code, opening pull requests, or deploying OpenChainBench. They explain which guides to read, where changes should merge, and how staging previews work.
Why use it?
They prevent outdated Next.js assumptions and reduce the risk of deploying unfinished changes to the live site.

Instructions file for CodexOpenCode

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

This is ChainBench/OpenChainBench's own configuration. It tells Codex and OpenCode how to work on OpenChainBench 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 OpenChainBench configures →

not rated 8repo yesterday A scan 467 tokens original MIT
View source ↗ ChainBench/OpenChainBench openchainbench.com
Reuse

Borrowing it

Nothing to install: this file belongs to ChainBench/OpenChainBench. 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/ChainBench/OpenChainBench/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/ChainBench/OpenChainBench

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 OpenChainBench AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/chainbench/openchainbench/agents-md"><img src="https://agentmods.dev/badge/instructions/chainbench/openchainbench/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 467 This file is loaded in full into every session.
When invoked 467 The same file — it is already loaded in full.
Security scan A 0 findings. 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.00467 $0.00467
Opus 5.5 $0.00187 $0.00187
Sonnet 5.5 $0.00093 $0.00093
Haiku 4.5 $0.00047 $0.00047

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

Security

Grade A, and why

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

AGENTS.md · 27 lines

What it actually says

This is NOT the Next.js you know

This version has breaking changes. APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.

Branch workflow

Two long-lived branches:

  • main → openchainbench.com (production). Every push to main triggers .github/workflows/prod-deploy.yml which runs vercel --prod automatically via CI.
  • dev → staging. Each push triggers .github/workflows/staging-deploy.yml which calls Vercel CLI with a token and emits a Preview URL.

Standard flow:

  1. Open a feature branch from dev: git checkout dev && git pull && git checkout -b feat/your-thing
  2. PR feat/your-thing → dev (NOT main). After merge, the staging Action posts a Preview URL in the workflow summary.
  3. Review on the Preview URL.
  4. When the staging state looks ready to ship, open a PR dev → main. After merge, prod-deploy.yml runs automatically.

Rules:

  • Never push directly to main or dev. PRs only.
  • The staging URL emits <meta robots=noindex> and serves robots.txt: Disallow /, see src/app/robots.ts and src/app/layout.tsx. Don't undo without thinking through duplicate-content SEO impact on the prod domain. Vercel Preview SSO is disabled (URL is publicly shareable), so the noindex is the only thing keeping crawlers out.
  • Hotfix path: if prod is on fire and waiting through dev is unacceptable, open the fix PR directly against main, merge (CI deploys automatically), then immediately fast-forward dev from main (git checkout dev && git merge --ff-only main && git push) so the two branches don't diverge.
  • Required GitHub secrets (repo-level, not environment-scoped): VERCEL_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID.
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 · 27 lines · 467 tokens per session scan A 4cbdb914b17a

Subscribe to this mod's changes

OpenChainBench AGENTS.md is an instructions file published in the GitHub repository ChainBench/OpenChainBench (8 stars, last pushed yesterday), licensed MIT. It adds 467 tokens to every session, about $0.0019 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-31.

apibenchmarkcryptodataopen-sourcereproductible
Related

OpenChainBench AGENTS.md compared with instructions from other repositories

OpenChainBench AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
OpenChainBench AGENTS.mdChainBench/OpenChainBenchInstructions file8yesterdayMITA467Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode