terminal-bench-1: Instructions file for Claude Code

CLAUDE.md

terminal-bench-1 CLAUDE.md is an instructions file for Claude Code from harbor-framework/terminal-bench-1. It costs 790 tokens per session, scanned A, original, Apache-2.0.

A repository instruction document for Terminal-Bench, a benchmark that tests coding agents in real terminal environments.

In plain words
What is it for?
It is for navigating the Python package, task definitions, agent integrations, harness, datasets, registries, and benchmark adapters, and for running tasks.
Why use it?
It gives an agent the project structure and standard commands needed to work consistently in the repository.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is harbor-framework/terminal-bench-1's own configuration. It tells Claude Code how to work on terminal-bench-1 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 terminal-bench-1 configures →

About the project

Terminal-Bench is a benchmark and execution harness for testing whether AI agents can complete difficult, end-to-end tasks in real terminal environments. It is used by developers of language-model agents and benchmarking systems, with tasks covering activities such as compiling code, training models, and setting up servers. Catalogue add-ons help agents work with the benchmark and its task suite.

harbor-framework/terminal-bench-1 · 2,612 stars · on GitHub · tbench.ai

Reuse

Borrowing it

Nothing to install: this file belongs to harbor-framework/terminal-bench-1. 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/harbor-framework/terminal-bench-1/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/harbor-framework/terminal-bench-1

Made for: Claude Code.

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 terminal-bench-1 CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/harbor-framework/terminal-bench-1/claude-md/github.svg)](https://agentmods.dev/instructions/harbor-framework/terminal-bench-1/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/harbor-framework/terminal-bench-1/claude-md"><img src="https://agentmods.dev/badge/instructions/harbor-framework/terminal-bench-1/claude-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 terminal-bench-1 CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/harbor-framework/terminal-bench-1/claude-md"><img src="https://agentmods.dev/badge/instructions/harbor-framework/terminal-bench-1/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 790 This file is loaded in full into every session.
When invoked 790 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.00790 $0.00790
Opus 5.5 $0.00316 $0.00316
Sonnet 5.5 $0.00158 $0.00158
Haiku 4.5 $0.00079 $0.00079

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

Security

Grade A, and why

terminal-bench-1 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 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.

CLAUDE.md · 117 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Overview

Terminal-Bench (T-Bench) is a benchmark for testing AI agents in real terminal environments. It consists of a dataset of tasks and an execution harness that connects language models to a sandboxed terminal environment.

Architecture

Core Components

  • terminal_bench/: Main Python package

    • cli/tb/: Command-line interface implementation
    • agents/: Agent implementations for various LLMs
    • harness/: Execution harness for running tasks
    • dataset/: Dataset handling and management
    • registry/: Task registry management
    • llms/: Language model integrations
    • terminal/: Terminal environment handling
  • tasks/: Individual task implementations

    • Each task has its own directory with instruction, docker environment, test script, and reference solution
    • Tasks include Python, shell scripts, C, Rust, and other languages
  • adapters/: Adapters for other benchmarks (SWE-bench, USACO, etc.)

Common Development Commands

Running Tasks

# Run the harness with specific agent and model
tb run --agent terminus --model anthropic/claude-3-7-latest

# Run specific tasks
tb run --task-id "task-name" --agent terminus --model model-name

# Run with dataset version
tb run --dataset terminal-bench-core==0.1.1

Testing

# Run all tests
uv run pytest tests/ -v

# Run specific test file
uv run pytest tests/unit/test_file.py -v

# Run with coverage
uv run pytest tests/ --cov

Linting and Code Quality

# Run Ruff linter
uvx ruff check .

# Fix auto-fixable issues
uvx ruff check . --fix

Task Management

# List available tasks
tb tasks list

# Create a new task (follow the documentation)
tb tasks create

Development Guidelines

Python Style

  • Python 3.13+ is used
  • Use type hints for all functions
  • Private methods have _ prefix
  • Use modular design, avoid deep nesting
  • Use modern type annotations: list, dict, | instead of List, Dict, Union

Read the full file on GitHub · 117 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 · 117 lines · 790 tokens per session scan A ef5031f6f33b

Subscribe to this mod's changes

terminal-bench-1 CLAUDE.md is an instructions file published in the GitHub repository harbor-framework/terminal-bench-1 (2,612 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 790 tokens to every session, about $0.0032 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,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,731 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