Borrowing it
Nothing to install: this file belongs to actava-ai/chi-bench. 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/actava-ai/chi-bench/main/CLAUDE.mdgit clone --depth 1 https://github.com/actava-ai/chi-benchWrote 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/actava-ai/chi-bench/claude-md)<a href="https://agentmods.dev/instructions/actava-ai/chi-bench/claude-md"><img src="https://agentmods.dev/badge/instructions/actava-ai/chi-bench/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.
<a href="https://agentmods.dev/instructions/actava-ai/chi-bench/claude-md"><img src="https://agentmods.dev/badge/instructions/actava-ai/chi-bench/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.05106 | $0.05106 |
| Opus 5.5 | $0.02042 | $0.02042 |
| Sonnet 5.5 | $0.01021 | $0.01021 |
| Haiku 4.5 | $0.00511 | $0.00511 |
Grade A, and why
chi-bench CLAUDE.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Anthropic Console setting, not a harness/config bug. Reproduce with a bare curl before How it starts
The opening of the file, as written. The whole thing — 287 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.
Self-improvement protocol
This file is a living document. Whenever a session in this repo would have gone smoother with a note here, edit CLAUDE.md before ending the turn — don't wait to be asked. Future sessions inherit this file but inherit nothing else from this one.
Triggers — add or update an entry when you notice any of these:
- The user corrects an approach ("no", "not that", "stop doing X", "again, like I said before"). → capture the rule and why (the reason the user gave, often a past incident).
- The user says "again" or you re-discover something already explained earlier in the session or in a prior session. Rediscovery = missing note.
- You hit the same error, friction point, or wrong-first-guess that has come up before (within this session or across sessions). One repeat is enough; don't wait for three.
- A command, path, env var, or convention was non-obvious and required grep / multiple file reads to locate.
- The user validates a non-obvious choice ("yes exactly", "that was the right call", accepting an unusual approach without pushback). Capture confirmations too — without them, future-you drifts away from validated approaches and re-litigates them.
- A command in the Commands section turned out to be wrong, stale, or missing a flag.
How to update:
- Add the note to the most relevant existing section (Commands, Things to remember, Architecture, Subdirectory note) rather than spawning new sections.
- Format: one-line rule first, then Why: clause when the reasoning is non-obvious, then optionally How to apply: when the trigger condition isn't obvious from the rule.
- If an existing item is wrong or stale, fix or delete it — don't accumulate cruft. CLAUDE.md is read in full at the start of every session; entries past line ~200 lose weight.
- Keep entries actionable and specific. "Be careful with X" is useless; "Run
foobeforebar, otherwise SQLite is left in state Y" is useful. - Mention CLAUDE.md updates in your end-of-turn summary so the user can review the diff.
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.
- 4d ago Changed · -4 lines · +351 tokens per session 08943cd8b03b
- 22d ago Changed · +18 lines · +334 tokens per session 1d35e97b18b0
- 2mo ago First seen · 273 lines · 4,421 tokens per session scan A a51181512fa0
chi-bench CLAUDE.md is an instructions file published in the GitHub repository actava-ai/chi-bench (73 stars, last pushed 4d ago), licensed Apache-2.0. It adds 5,106 tokens to every session, about $0.0204 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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).
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.
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).
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.