Borrowing it
Nothing to install: this file belongs to enricai/leerie. 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/enricai/leerie/main/CLAUDE.mdgit clone --depth 1 https://github.com/enricai/leerieWrote 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/enricai/leerie/claude-md)<a href="https://agentmods.dev/instructions/enricai/leerie/claude-md"><img src="https://agentmods.dev/badge/instructions/enricai/leerie/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/enricai/leerie/claude-md"><img src="https://agentmods.dev/badge/instructions/enricai/leerie/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.07385 | $0.07385 |
| Opus 5 | $0.03692 | $0.03692 |
| Sonnet 5 | $0.01477 | $0.01477 |
| Haiku 4.5 | $0.00739 | $0.00739 |
Grade A, and why
leerie 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 9d 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 — 514 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code working in this repository. Read docs/DESIGN.md
before touching architecture; read docs/IMPLEMENTATION.md before touching
code surface; read this file first.
Tech stack
Python 3.10+, stdlib-preferred orchestrator (runtime deps pinned in
requirements.txt and listed in docs/IMPLEMENTATION.md §0). The
orchestrator shells out to claude -p (Claude Code CLI, on the user's
subscription — no API key) and uses git worktrees for parallel
implementer isolation. pytest is the only dev dependency.
Leerie runs inside a container. The leerie launcher shells out to
nerdctl run to start a container per run (DESIGN §6 Worker subtree
termination). The orchestrator runs as PID 1 inside; every worker
(and every Bash tool call those workers make) lives in the same PID
namespace. On Ctrl-C / SIGTERM / SIGKILL / crash, the kernel reaps
the namespace — the abnormal-exit cleanup guarantee is the container
boundary, not Python signal handling.
Runtime: containerd + nerdctl. On Linux, native. On macOS, via
Colima (a Lima-managed Linux VM). See
docs/INSTALL.md for per-OS install steps.
Python is provisioned inside the container by the image (Python 3
from Debian 13). The launcher itself is a portable bash script; it
no longer needs uv or a host Python. See docs/IMPLEMENTATION.md
§0 (install surface) and §0.5 (container shape).
All control flow lives in one file: orchestrator/leerie.py. The
launcher (a portable bash script) and the Dockerfile are the only
other moving parts on the orchestrator side. The orchestrator is
deliberately kept as a single module rather than split across
packages — the design goal is that you can read the whole control
flow top-to-bottom in one sitting. Stdlib-preferred on the Python side
— runtime deps are pinned in requirements.txt and listed in
docs/IMPLEMENTATION.md §0; pytest is the sole dev dependency.
The three-layer rule (load-bearing — read first)
This repo deliberately separates theory, mechanism, and code, and the layers are top-down canonical: each layer derives from and conforms to the one above it.
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.
- 9d ago First seen · 514 lines · 7,385 tokens per session scan A bccdbd395e65
leerie CLAUDE.md is an instructions file published in the GitHub repository enricai/leerie (10 stars, last pushed 6d ago), licensed MIT. It adds 7,385 tokens to every session, about $0.0369 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-31.
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.
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.