Borrowing it
Nothing to install: this file belongs to alilee/cranelisp. 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/alilee/cranelisp/main/CLAUDE.mdgit clone --depth 1 https://github.com/alilee/cranelispWrote 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/alilee/cranelisp/claude-md)<a href="https://agentmods.dev/instructions/alilee/cranelisp/claude-md"><img src="https://agentmods.dev/badge/instructions/alilee/cranelisp/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.06213 | $0.06213 |
| Opus 5 | $0.03106 | $0.03106 |
| Sonnet 5 | $0.01243 | $0.01243 |
| Haiku 4.5 | $0.00621 | $0.00621 |
Grade A, and why
cranelisp 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cranelisp
First Steps
Before doing any work, find all CLAUDE.md files in the project:
glob **/CLAUDE.md
Before doing work in any directory, read all CLAUDE.md files in that directory and every parent directory up to the project root. Local CLAUDE.md files contain conventions and context specific to nearby files.
Project Layout
| Directory | Purpose |
|---|---|
spec/ |
Language specification — owned by spec (scribe; the user arbitrates semantics) |
design/ |
Architecture and per-crate implementation design — design/arch/ owned by arch, design/{crate}/ by design |
src/ |
Compiler binary crate — pipeline, REPL, CLI, session |
crates/ |
Bounded-context library crates (types, frontend, typecheck, backend, primitives, intrinsics, platform, exe-bundle) |
user/ |
User-facing documentation — owned by docs |
stdlib/ |
Standard library in Cranelisp — a dev surface |
examples/ |
Learning sequence — owned by training |
exemplar/ |
Showcase project (Sudoku Solver) — a dev surface |
repl/ |
REPL experience spec (spec), demos and harness (test) |
tests/ |
E2e suite — plan owned by qa, test sources by test |
audits/ |
Whole-context audit assessments — owned by audit |
sprints/ |
Delivery coordination — method, roadmap, current sprint, actions, archive — owned by sprint |
.agents/ |
The shared role package, pinned as a submodule (.agents/CONSUMING.md) |
Sketch Oracle (retired)
The prototype compiler that lived in sketch/ was deleted at the close of Sprint 87 (pre-Phase-H hygiene): language semantics are frozen, and the reimplementation's own references (design/{crate}/, audits/, spec/) long ago superseded it. If a spec ambiguity ever needs the original oracle's behaviour, recover the sketch from git history rather than treating it as a live reference. Historical mentions of the sketch throughout design/, sprints/, and audits/ are an accurate record of past consultations.
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 First seen · 270 lines · 6,213 tokens per session scan A 412c0cc0fad6
cranelisp CLAUDE.md is an instructions file published in the GitHub repository alilee/cranelisp (7 stars, last pushed 6d ago), licensed MIT. It adds 6,213 tokens to every session, about $0.0311 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-09-04.
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.