benchmark-radar: Instructions file for Codex

AGENTS.md

benchmark-radar AGENTS.md is an instructions file for Codex, OpenCode from ktwu01/benchmark-radar. It costs 1,879 tokens per session, scanned A, original, MIT.

Repository instructions for Benchmark Radar, a project that presents benchmark results and related information to readers. They explain how to write clear reports, interfaces, documentation, and other public-facing material.

In plain words
What is it for?
Use them when editing README files, documentation, dashboards, reports, launch notes, screenshots, demos, or other user-facing content.
Why use it?
They help keep the reader’s most useful result visible instead of hiding it behind implementation details.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 benchmark-radar AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/ktwu01/benchmark-radar/agents-md"><img src="https://agentmods.dev/badge/instructions/ktwu01/benchmark-radar/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,879 This file is loaded in full into every session.
When invoked 1,879 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.01879 $0.01879
Opus 5.5 $0.00752 $0.00752
Sonnet 5.5 $0.00376 $0.00376
Haiku 4.5 $0.00188 $0.00188

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

Security

Grade A, and why

benchmark-radar 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 4d 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 · 139 lines

How it starts

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

Repository Instructions

Read principle.md before changing a benchmark-facing surface. Its full-corpus coverage rule applies to charts, search, tables, counts, and exports: start from 1,259+ benchmark records across 4+ sources, and investigate any unexplained reduction to a few dozen. Missing measurements must not remove corpus records. Benchmark Frontier and its linked score ranking explicitly exclude records without numeric reported scores, as specified in principle.md.

Reference guides

This file holds the rules that apply to every change. Detailed procedure lives in the guides below. Each line states when the guide is required reading, and the constraint that holds whether or not you open it.

Guide Read it before Constraint that always holds
docs/pipeline-and-data-map.md Touching a source input, a generator, a generated artifact, or the technical report Never reconstruct the system from a report, the deployed site, or leftover generated files. Never patch a derived file to fix a source-data problem.
docs/sop-add-model-cards.md Adding a model card, a benchmark, or a score data/model_cards.yml and data/benchmark_scores.yml move together. Every value is read out of the cited document, never from memory.
docs/query-surfaces.md Changing search, detail lookup, the CLI or HTTP query surface, or the consumer Skill QueryService is the single source of truth. No interface-specific ranking, and no silent network fallback.
principle.md Changing any benchmark-facing surface Start from the full corpus across all sources.
docs/agent-gotchas.md Verifying locally, merging, or answering a literature question A local result counts only from a clean worktree with its own venv.
maintainer-review.md Reviewing or merging a contributor PR The human contributor answers the four questions, and the change takes the least resource-intensive route.

Read the full file on GitHub · 139 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. 4d ago Changed · +14 lines · +187 tokens per session 2ad282b18eb1
  2. 8d ago Changed · -9 lines · -93 tokens per session 3f3f3585215e
  3. 9d ago Changed · +4 lines · +82 tokens per session 69d374312cc2
  4. 19d ago Changed · -11 lines · -539 tokens per session 1b8a024b7e11
  5. 20d ago Changed · -6 lines · -184 tokens per session 3d585d269cce
  6. 1mo ago Changed · +13 lines · +230 tokens per session 8ca1c8cd3130
  7. 1mo ago Changed · -151 lines · -1,924 tokens per session acd3d0e0d2d4
  8. 1mo ago Changed · +6 lines · +85 tokens per session 7c126c18d754
  9. 1mo ago Changed · +40 lines · +650 tokens per session fef1e8379ad3
  10. 1mo ago First seen · 239 lines · 3,385 tokens per session scan A ef3cc236ac97

Subscribe to this mod's changes

benchmark-radar AGENTS.md is an instructions file published in the GitHub repository ktwu01/benchmark-radar (304 stars, last pushed yesterday), licensed MIT. It adds 1,879 tokens to every session, about $0.0075 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-30.

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,581 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

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.

deepseek-ai/deepseek-harness · 4,261 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,731 tokens