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.
npx agentmods add instructions/tiger-ai-lab/clawbench/agents-mdgit clone --depth 1 https://github.com/TIGER-AI-Lab/ClawBenchWrote 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/tiger-ai-lab/clawbench/agents-md)<a href="https://agentmods.dev/instructions/tiger-ai-lab/clawbench/agents-md"><img src="https://agentmods.dev/badge/instructions/tiger-ai-lab/clawbench/agents-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 | $0.01789 | $0.01789 |
| Opus 5 | $0.00894 | $0.00894 |
| Sonnet 5 | $0.00358 | $0.00358 |
| Haiku 4.5 | $0.00179 | $0.00179 |
Grade A, and why
ClawBench 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 today.
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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClawBench -- Agent Context
This file is for coding agents (Claude Code, Cursor, Copilot, etc.) to understand and operate on the ClawBench project. If you are a human, see the README.
What This Is
ClawBench is a benchmarking framework for evaluating AI web agents on real-world online tasks. V1 lives in test-cases/v1/ with 152 tasks spanning 143 live websites and 15 life categories; V2 lives in test-cases/v2/ with 129 tasks; Lite lives in test-cases/v1-lite/ with 20 link-backed V1 tasks. Each task runs in an isolated Docker container with a browser, a recording Chrome extension, and an AI agent harness (openclaw, opencode, claude-code, claude-code-chrome-extension, codex, browser-use, claw-code, hermes, or pi, or webbrain, selectable via --harness). The framework captures five layers of data: session replay (MP4), action screenshots, HTTP traffic, browser actions, and agent messages.
Project Structure
ClawBench/
run.sh # Entry point -- launches interactive TUI
pyproject.toml # Root uv package metadata and CLI scripts
.env # Shared PurelyMail credentials packaged with the CLI
src/
clawbench/ # Main Python package
tui.py # Interactive TUI (called by run.sh)
runner/
run.py # Single test-case runner
batch.py # Batch runner (model x case cross-product)
run_support/ # Runner-private helpers for single runs
utils/
hf_upload.py # Optional HuggingFace upload helpers
runtime/
shared/
alex_green_personal_info.json
runtime-server/ # Container-only uv project for server deps
chrome-extension/ # Recording extension
harnesses/ # Dockerfiles + setup/run scripts
models/
models.yaml # Model API configs (gitignored -- copy from example)
models.example.yaml # Template with placeholder keys
model.schema.json # JSON schema for model entries
test-cases/
task.schema.json # JSON schema for task.json
v1/ # V1: 152 task directories
v2/ # V2: 129 task directories
v1-lite/ # Lite: 20 V1 task directories with linked task files
eval/
README.md # Evaluation guide + Claude Code prompt template
agentic_eval.md # Evaluator rubric for judging agent success
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.
- today Changed · +4 lines · +110 tokens per session bc7e4bd18194
- 5d ago First seen · 146 lines · 1,679 tokens per session scan A a0a6e404a594
ClawBench AGENTS.md is an instructions file published in the GitHub repository TIGER-AI-Lab/ClawBench (639 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,789 tokens to every session, about $0.0089 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
browser-use AGENTS.md
AGENTS.md instructions for browser-use/browser-use, covering agents.md version 2, development rules, quickstart, 1. installing browser-use and on windows use .venv\scripts\activate.
browser-use CLAUDE.md
Claude Code instructions for browser-use/browser-use, covering claude.md, high-level architecture, core components, event-driven browser management and cdp integration.
browser-harness AGENTS.md
AGENTS.md instructions for browser-use/browser-harness, covering code priorities, commands, doctor — install/daemon/browser state, unit tests (no live browser) and security.
browser-harness CLAUDE.md
Claude Code instructions for browser-use/browser-harness, a project described as: Browser Harness | Self-healing harness that enables LLMs to complete any task.
AIPex AGENTS.md
Instructions for AIPexStudio/AIPex, covering package architecture, building and running, writing tests, test structure and framework and mocking (vi from vitest).
terminal AGENTS.md
Instructions for browser-use/terminal, covering agent notes, rust rewrite verification loop and terminal ui testing standard.