Borrowing it
Nothing to install: this file belongs to WildChildForLife/lantern. 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/WildChildForLife/lantern/main/CLAUDE.mdgit clone --depth 1 https://github.com/WildChildForLife/lanternWrote 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/wildchildforlife/lantern/claude-md)<a href="https://agentmods.dev/instructions/wildchildforlife/lantern/claude-md"><img src="https://agentmods.dev/badge/instructions/wildchildforlife/lantern/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.01636 | $0.01636 |
| Opus 5 | $0.00818 | $0.00818 |
| Sonnet 5 | $0.00327 | $0.00327 |
| Haiku 4.5 | $0.00164 | $0.00164 |
Grade A, and why
lantern CLAUDE.md scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- `Command.string` instead of `child_process` This is a copy
86% identical to lantern AGENTS.md — 71 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Critical Rules (Read First)
Language:
- Code, comments, commits in English
NEVER:
- Use
astype casting anywhere, tests included (explain problem to user instead) - Use raw
fetchor bypass TanStack Query for API calls - Run
pnpm devorpnpm start(dev servers) - Use
node:fs,node:path, etc. directly (use Effect-TS equivalents)
ALWAYS:
- Effect-TS for all backend side effects
- Hono RPC + TanStack Query for all API calls
- TDD: tests first, then implement
- Run
pnpm typecheckandpnpm fixbefore commit
Commit Message Rules
Conventional Commits: type: description
Release Note Awareness:
- Commit messages ship in release notes. Write for users.
Type Selection:
| Type | Release Note | Purpose |
|---|---|---|
feat |
Features | User-facing new feature |
fix |
Bug Fixes | User-impacting bug fix |
chore, ci, build, refactor |
Excluded | Internal changes |
Critical: fix only for user-facing bugs. Internal fixes (linter errors, type errors, build scripts) use chore.
Message Quality Examples:
- Bad:
fix: fix lingui error(internal issue) - Bad:
feat: add button(too vague) - Good:
feat: add dark mode toggle to settings - Good:
fix: session list not updating after deletion - Good:
chore: update lingui compiled messages
Project Overview
Lantern reads Claude Code session logs straight from JSONL files (~/.claude/projects/), zero data loss. Web client built as CLI tool serving Vite app.
Core Architecture:
- Frontend: Vite + TanStack Router + React 19 + TanStack Query
- Backend: Hono (standalone server) + Effect-TS (all business logic)
- Data: Direct JSONL reads, strict Zod validation
- Real-time: Server-Sent Events (SSE) for live updates
Recommended Coding Process
Project aims for fast feedback AND code quality (checks pass = runtime correctness near-guaranteed) via:
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 · 202 lines · 1,636 tokens per session scan A 10df52943d98
lantern CLAUDE.md is an instructions file published in the GitHub repository WildChildForLife/lantern (28 stars, last pushed today), licensed MIT. It adds 1,636 tokens to every session, about $0.0082 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). It is 86% identical to lantern AGENTS.md, differing in 71 lines, and is treated as a copy.
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.