Borrowing it
Nothing to install: this file belongs to aileron-sh/aileron. 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/aileron-sh/aileron/main/CLAUDE.mdgit clone --depth 1 https://github.com/aileron-sh/aileronWrote 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/aileron-sh/aileron/claude-md)<a href="https://agentmods.dev/instructions/aileron-sh/aileron/claude-md"><img src="https://agentmods.dev/badge/instructions/aileron-sh/aileron/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.01055 | $0.01055 |
| Opus 5 | $0.00528 | $0.00528 |
| Sonnet 5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
aileron 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 7d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - Aileron
Aileron is a tamper-evident flight recorder for AI agents: a hash-chained journal of every tool
call, Ed25519-signed checkpoints, policy enforcement before execution, and offline verification.
Apache-2.0, pure Python ≥3.10, two runtime dependencies (pyyaml, cryptography).
This is a security tool that is published on PyPI. Changes here are changes to something people rely on to tell them what their agents did. Bias toward correctness and honesty over speed.
The four invariants
Break any of these and the product is no longer what it claims to be.
- Canonical JSON is the hash input.
events.canonical_json()is the single serializer the chain and signatures depend on - sorted keys, tight separators,ensure_ascii=True,allow_nan=False. Never hand-format event JSON, and never add a second copy of this function. Changing it changes every hash and invalidates existing journals. capture_contentgates persistence, not enforcement. Policy rules and the anomaly detector always see the full call in memory;ChainLog.appendstrips content from the copy it writes. Rules must fire in the default digest-only mode.- A prefilter may only ever skip work, never a detection.
prefilter.pylets the policy engine skip a rule's regex when the payload provably cannot match it. Wrongly skipping is a rule that silently stops firing and a journal that looks clean, so everything there is deliberately lopsided: anything not understood returnsNone, meaning "run the regex".fold()is proven sound over every Unicode codepoint by a test, becausestr.lower()andstr.casefold()are both quietly wrong againstre.IGNORECASE. SetAILERON_NO_PREFILTER=1to rule it out during an investigation. - A checkpoint signs a prefix. Appending after signing stays valid; truncating or rewriting
the signed prefix does not. Checkpoints are chained to each other (
index,prev_checkpoint_hash).
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.
- 7d ago First seen · 84 lines · 1,055 tokens per session scan A ab42a1770fa2
aileron CLAUDE.md is an instructions file published in the GitHub repository aileron-sh/aileron (1 stars, last pushed today), licensed Apache-2.0. It adds 1,055 tokens to every session, about $0.0053 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.