Borrowing it
Nothing to install: this file belongs to blackpaw-studio/leo. 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/blackpaw-studio/leo/main/CLAUDE.mdgit clone --depth 1 https://github.com/blackpaw-studio/leoWrote 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/blackpaw-studio/leo/claude-md)<a href="https://agentmods.dev/instructions/blackpaw-studio/leo/claude-md"><img src="https://agentmods.dev/badge/instructions/blackpaw-studio/leo/claude-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.1 | $0.01779 | $0.01779 |
| Opus 5 | $0.00890 | $0.00890 |
| Sonnet 5 | $0.00356 | $0.00356 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade A, and why
leo 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 6d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository agent guidance
This file provides shared guidance to coding agents working in this repository. AGENTS.md is a symlink to this file so Claude Code and Codex use one source of truth.
What is Leo
Leo is a Go CLI that supervises Claude Code agents and schedules tasks. leo service runs the daemon — web UI, cron, agent supervision, and the IPC socket — which keeps ephemeral agents alive, each in its own tmux session. Channels (Telegram, Slack, webhook, etc.) are Claude Code plugins the user installs separately; Leo only knows them as opaque plugin IDs.
Two core primitives:
- Agents (
leo agent): spawn/list/attach/stop/suspend/resume/reset/logs for on-demand agents created from templates, supervised by the daemon with restart-on-crash. Dual-purpose — runs locally against the daemon, or acts as a thin SSH client against a remote leo host whenclient.hostsis configured. Agents can idle-suspend after inactivity and auto-resume on the next message. - Tasks (
leo run <task>, cron-scheduled): defaultruntime: oneshotinvokes a freshclaude -pper firing; the agent handles outbound messaging via whatever channel plugin(s) are configured.runtime: persistentinstead injects the prompt into a supervised agent —template: <name>targets that template's agent explicitly (shareable across tasks), or an implicit agent named after the task is spawned/resumed on demand ("ensure-exists") when notemplate:is set. Seedocs/configuration/persistent-tasks.md.
Build & Test Commands
make build # Build binary to bin/leo
make install # go install
make test # go test -race -cover ./...
make lint # go vet + staticcheck
make snapshot # goreleaser snapshot
# Run a single test
go test -race -run TestFunctionName ./internal/config/
# Coverage report
go test -race -coverprofile=coverage.out ./... && go tool cover -html=coverage.out
Version is injected via ldflags: -X github.com/blackpaw-studio/leo/internal/cli.Version=$(VERSION)
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.
- 6d ago First seen · 90 lines · 1,779 tokens per session scan A 715254ac9a68
leo CLAUDE.md is an instructions file published in the GitHub repository blackpaw-studio/leo (5 stars, last pushed yesterday), licensed MIT. It adds 1,779 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-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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.