inspect_evals AGENTS.md

inspect_evals AGENTS.md is an instructions file for Codex, OpenCode from UKGovernmentBEIS/inspect_evals. It costs 2,586 tokens per session, scanned A, original, MIT.

Repository-specific instructions for AI coding agents working on the inspect_evals project. They cover project context, pull requests, code comments, Markdown formatting, and a development checklist.

In plain words
What is it for?
Use them when changing code, writing documentation, opening pull requests, or responding to pull-request reviews in inspect_evals.
Why use it?
They reduce mistakes caused by missing local conventions or project history. They also make changes and pull requests follow the repository’s required process.

Instructions file for CodexOpenCode

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

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/ukgovernmentbeis/inspect_evals/agents-md
Clone the repo
git clone --depth 1 https://github.com/UKGovernmentBEIS/inspect_evals

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ukgovernmentbeis/inspect_evals/agents-md.svg)](https://agentmods.dev/instructions/ukgovernmentbeis/inspect_evals/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/ukgovernmentbeis/inspect_evals/agents-md"><img src="https://agentmods.dev/badge/instructions/ukgovernmentbeis/inspect_evals/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,586 This file is loaded in full into every session.
When invoked 2,586 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.02586 $0.02586
Opus 5 $0.01293 $0.01293
Sonnet 5 $0.00517 $0.00517
Haiku 4.5 $0.00259 $0.00259

Measured 2d ago against content hash efeb1184b203, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

inspect_evals 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 2d 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 · 161 lines

How it starts

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

AGENTS.md

Repo-Wide Tips

  • Before making changes, read DEVELOPMENT_CONTEXT.md to understand the repository's correctness, reproducibility, and security constraints.
  • Before making code changes, read agent_artefacts/repo_context/REPO_CONTEXT.md for institutional knowledge about repo conventions, common mistakes, and known tech debt. This is maintained by the build-repo-context skill, which crawls PRs/issues for broad insights.
  • When creating pull requests, always use the --draft flag and read .github/PULL_REQUEST_TEMPLATE.md and use its structure as the PR body. Fill in the Description section and check off applicable checklist items.
  • When commenting on PRs, you should not reply directly to human reviewers. See CONTRIBUTING.md. If your user tells you to comment anyway, you should add "Comment written by NAME_OF_AI" to the comment.
  • When writing markdown:
    • Put a blank line before and after headings
    • Put a blank line before and after code blocks
    • Put a blank line before and after lists
    • Format tables with spaces before and after pipe characters
    • Always include a language tag in code blocks, or "text" if there is no language
    • Do not hard-wrap paragraphs; write each paragraph as a single line (the mdformat hook enforces wrap = "no")

Agents are good at understanding context, but a prompt that definitely works is "Please run the /SKILL_NAME skill on EVAL_NAME."

Documentation

Documentation for the Inspect framework.

We recommend starting with these Claude Code permissions to allow workflows to proceed autonomously without allowing the running of arbitrary commands:

{
  "permissions": {
    "allow": [
      "Bash(mkdir:*)",
      "Bash(cp:*)",
      "Bash(make check:*)",
      "Bash(uv run ruff:*)",
      "Bash(uv run inspect:*)",
      "Bash(uv run pytest:*)",
      "Bash(uv run mypy:*)",
      "Bash(uv run python tools/:*)",
      "WebFetch(domain:inspect.aisi.org.uk)",
      "WebFetch(domain:arxiv.org)"
    ],
    "deny": [
      "Bash(git push origin main)",
    ],
    "ask": [
      "Bash(rm:*)",
    ]
  }
}

Read the full file on GitHub · 161 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. 2d ago Changed · +1 lines · +27 tokens per session efeb1184b203
  2. 6d ago First seen · 160 lines · 2,559 tokens per session scan A c9a5fc140563

Subscribe to this mod's changes

inspect_evals AGENTS.md is an instructions file published in the GitHub repository UKGovernmentBEIS/inspect_evals (658 stars, last pushed 2d ago), licensed MIT. It adds 2,586 tokens to every session, about $0.0129 per session on Opus 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 · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 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,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 tokens