Borrowing it
Nothing to install: this file belongs to lacerbi/dotclaude. 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/lacerbi/dotclaude/main/CLAUDE.mdgit clone --depth 1 https://github.com/lacerbi/dotclaudeWrote 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/lacerbi/dotclaude/claude-md)<a href="https://agentmods.dev/instructions/lacerbi/dotclaude/claude-md"><img src="https://agentmods.dev/badge/instructions/lacerbi/dotclaude/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/lacerbi/dotclaude/claude-md"><img src="https://agentmods.dev/badge/instructions/lacerbi/dotclaude/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.01730 | $0.01730 |
| Opus 5.5 | $0.00692 | $0.00692 |
| Sonnet 5.5 | $0.00346 | $0.00346 |
| Haiku 4.5 | $0.00173 | $0.00173 |
Grade A, and why
dotclaude 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 yesterday.
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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shell tooling
The user is on Windows PowerShell. @'...'@ here-strings work only in the PowerShell tool, not the Bash tool (and <<'EOF' only in Bash). For multi-line text like commit messages, use repeated -m flags.
Smoke tests / long runs must stream output. Don't pipe python ... | grep — a non-TTY pipe makes Python block-buffer stdout, so nothing shows until it exits. -u (or PYTHONUNBUFFERED=1) is the key bit; have the script print(..., flush=True) on a cadence so there's something to watch.
- Local: run unbuffered to a uniquely-named log (don't clobber a prior run):
python -u script.py > runs/run_$(date +%s).log 2>&1(background ok), then Read/tail -Fit. Filter when reading (grepthe file), not in the run pipe. - HPC: don't hand-redirect — Slurm captures each job's stdout to its own per-jobid file (so no clobber across runs). Use
hpc logs <job> --once/-n Nfor occasional dumps, orhpc logsto follow. The script still needs periodicflush=Trueso the Slurm log updates before the job ends.
Commit messages
Leave the session link out of commit messages and pull request descriptions: no Claude-Session: trailer and no claude.ai/code/session_… URL. Keep the Co-Authored-By: line.
Python environments
Create venvs with uv (uv venv + uv pip install -r requirements.txt, or uv sync with a pyproject.toml), not python -m venv + pip. uv hardlinks packages from its cache, so venvs on the same package versions share disk; pip copies everything, and a CUDA torch venv is ~4.5 GB. Keep one venv per project, since projects pin different torch builds and install different editable sources. Install CPU torch unless the project actually runs on GPU, and when nothing pins the torch version, match a version that other local venvs already use, so the cached wheel is reused.
Agent Selection
Sub-agents are Opus by default (model: opus) — exploration, review, verification, and implementation alike. Use Sonnet only for narrow, fully specified mechanical work where no judgment is needed (run a linter or test suite and report the result; apply a spelled-out edit). Never Haiku: it is a generation behind and can't be trusted with interpretation. Fable sub-agents only when the user asks for them — too expensive to spawn routinely.
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.
- yesterday Changed · +2 lines · +66 tokens per session f27332608e2b
- 3d ago Changed · +17 lines · +568 tokens per session 4a0aa5317140
- 12d ago Changed · +4 lines · +146 tokens per session d4d1daf7e0b9
- 1mo ago Changed · +2 lines · +282 tokens per session 397a82fe50fb
- 1mo ago First seen · 26 lines · 668 tokens per session scan A 32cee759c6cd
dotclaude CLAUDE.md is an instructions file published in the GitHub repository lacerbi/dotclaude (2 stars, last pushed 2d ago), licensed MIT. It adds 1,730 tokens to every session, about $0.0069 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-31.
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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.