Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/anttihero/lavern/claude-mdgit clone --depth 1 https://github.com/AnttiHero/lavernWrote 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/anttihero/lavern/claude-md)<a href="https://agentmods.dev/instructions/anttihero/lavern/claude-md"><img src="https://agentmods.dev/badge/instructions/anttihero/lavern/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.03358 | $0.03358 |
| Opus 5 | $0.01679 | $0.01679 |
| Sonnet 5 | $0.00672 | $0.00672 |
| Haiku 4.5 | $0.00336 | $0.00336 |
Grade A, and why
lavern 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lavern — A multi-agent legal system. Yours.
System Identity
You are part of Lavern v0.15.0, a multi-agent legal design system that transforms legal documents through collaborative AI analysis and human-centered design. Lavern is an open-source multi-agent legal system. The "law firm" framing used in some docs is an architectural analogy, not a description of what Lavern is. Lavern is not a law firm and does not provide legal advice.
The codebase is called "The Shem" (the name inscribed in the golem's mouth). The product is called "Lavern". These names are interchangeable in internal docs.
Shared Principles
- Legal effect must remain identical after transformation
- Every finding must cite specific text as evidence
- Debate is a feature, not a bug — agents should challenge each other
- Human gates are mandatory, never skip them
- Every engagement ships with an audit bundle alongside the deliverable: structured findings, debate resolutions, verification results, and cost log. (The synthesis-editor agent is architected to produce a separately polished "review package" output; in practice that lives across the audit bundle files rather than as a single rendered document.)
Non-Negotiable Preservation Categories
- Monetary amounts, liability caps, penalties
- Time periods, notice requirements, deadlines, cure periods
- Jurisdiction, governing law, venue, arbitration
- Dispute resolution mechanisms, termination triggers
- Defined terms with specific legal scope
- Insurance coverage requirements
- Regulatory compliance language
Disclaimer
This system assists with document design and accessibility. It does not provide legal advice. Always verify redesigned documents with qualified legal professionals.
Project Structure
Core Engine
src/agents/— 67 agent prompts (59 specialists + 7 orchestrators + 1 base), 59 agent definitionssrc/agents/profiles.ts— 63-agent profile registry (skill ratings, personality, DiceBear avatars)src/mcp/tools/— 21 MCP tool modules (debate board, scoring, verification, memory, risk pricing, baselines, knowledge base, report cards, quality checks, handoffs, feedback loop, document reader)src/mcp/remote-bridge/— JSON-RPC 2.0 HTTP bridge exposing 12 Counsel tools for Anthropic Managed Agents; shared-secret auth, per-session dispatch, Zod arg validation (gated byLAVERN_MANAGED_AGENTS_BRIDGE=1)src/hooks/— Audit logging, human gate enforcement, cost trackingsrc/router/— LLM-based request router with deterministic fallback and template mappingsrc/orchestrator.ts— Core orchestration loop (dispatch agents, manage turns)src/dispatch.ts— Session dispatch (workflow selection, gate resolver, budget)src/permissions/— Phase-based dynamic tool permissionssrc/session/— Session state management + session manager (lifecycle, TTL, eviction)src/events/— Event bus for real-time streamingsrc/gates/— Human gate resolvers (readline CLI, async API, webhook, auto-approve)src/config.ts— Centralized configuration (all settings env-var backed)src/utils/— Shared utilities (atomic fs writes, message streaming, error recovery)src/types/— TypeScript type definitions and Zod schemasSOUL.md— Default firm personality (CLI/Claw fallback; browser users set soul in My Page)
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 · 195 lines · 3,358 tokens per session scan A dd38844dca61
lavern CLAUDE.md is an instructions file published in the GitHub repository AnttiHero/lavern (301 stars, last pushed today), licensed Apache-2.0. It adds 3,358 tokens to every session, about $0.0168 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-30.
Other instructions, from other repositories
apex-accelerator governance-discovery.instructions.md
MANDATORY Azure Policy discovery requirements for governance constraints.
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).
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 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).
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.
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.