Borrowing it
Nothing to install: this file belongs to UKGovernmentBEIS/inspect_evals. 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/UKGovernmentBEIS/inspect_evals/main/CLAUDE.mdgit clone --depth 1 https://github.com/UKGovernmentBEIS/inspect_evalsWrote 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/ukgovernmentbeis/inspect_evals/claude-md)<a href="https://agentmods.dev/instructions/ukgovernmentbeis/inspect_evals/claude-md"><img src="https://agentmods.dev/badge/instructions/ukgovernmentbeis/inspect_evals/claude-md.svg" alt="Measured on agentmods" 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.00613 | $0.00613 |
| Opus 5 | $0.00307 | $0.00307 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
inspect_evals CLAUDE.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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Instructions
This is the inspect_evals repository - a collection of evaluation tasks for the Inspect AI framework.
Running Commands
This project uses uv (by Astral) for package management. Do not use pip install, python -m venv, source .venv/bin/activate, or bare python/pytest commands. Always use uv to run commands:
uv sync— install/sync dependencies (replacespip install -e .)uv run pytest ...— run tests (notpytestorpython -m pytest)uv run python ...— run Python scripts (notpythonorpython3)uv run inspect eval ...— run evaluationsuv run ruff ...— run the linteruv run mypy ...— run the type checker
Note: uv is Astral's Python package manager. It is not related to uvicorn (an ASGI web server) — do not confuse them.
Contributing
For development setup, submission requirements, and contribution guidelines, see CONTRIBUTING.md.
Coding Style
When writing or modifying code in this repository, follow the guidelines in BEST_PRACTICES.md. Pay particular attention to the Writing comments section before adding any comments.
Markdown prose must not be hard-wrapped - write each paragraph as a single line. This is enforced by the mdformat pre-commit hook (configured in .mdformat.toml); see the markdown rules in AGENTS.md. Running uv run make check before completing your code ensures all markdown files are correctly formatted.
Evaluation Checklist
When creating or reviewing evaluations, refer to EVALUATION_CHECKLIST.md.
Versioning
For when to bump the inspect evals changelog, see PACKAGE_VERSIONING.md
For when to bump an inspect evals task version, see TASK_VERSIONING.md
Workflows
For common workflows (fixing evals, reviewing evals, making evaluation reports, checking agent trajectories, etc.), see AGENTS.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.
- 8d ago First seen · 49 lines · 613 tokens per session scan A c5f68902b361
inspect_evals CLAUDE.md is an instructions file published in the GitHub repository UKGovernmentBEIS/inspect_evals (662 stars, last pushed today), licensed MIT. It adds 613 tokens to every session, about $0.0031 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.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.