lgrep: Instructions file for Claude Code

CLAUDE.md

lgrep CLAUDE.md is an instructions file for Claude Code from dennisonbertram/lgrep. It costs 589 tokens per session, scanned A, original, MIT.

Project instructions for lgrep, a tool that searches code by meaning rather than only matching exact words. They also explain how to prepare the project and keep each worktree's files separate.

In plain words
What is it for?
Use them to initialize the project, check its setup, search the repository, investigate code changes, run type checks, and run tests.
Why use it?
They provide a consistent setup and exploration routine, reducing confusion when several worktrees or code-search indexes are involved.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions Codex.

This is dennisonbertram/lgrep's own configuration. It tells Claude Code how to work on lgrep itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything lgrep configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dennisonbertram/lgrep. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dennisonbertram/lgrep/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/dennisonbertram/lgrep

Made for: Claude Code.

Wrote 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.

agentmods badge for lgrep CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/dennisonbertram/lgrep/claude-md/github.svg)](https://agentmods.dev/instructions/dennisonbertram/lgrep/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/dennisonbertram/lgrep/claude-md"><img src="https://agentmods.dev/badge/instructions/dennisonbertram/lgrep/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for lgrep CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/dennisonbertram/lgrep/claude-md"><img src="https://agentmods.dev/badge/instructions/dennisonbertram/lgrep/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 589 This file is loaded in full into every session.
When invoked 589 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00589 $0.00589
Opus 5.5 $0.00236 $0.00236
Sonnet 5.5 $0.00118 $0.00118
Haiku 4.5 $0.00059 $0.00059

Measured 2mo ago against content hash a9d21e9b5a05, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lgrep 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 2mo 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.

CLAUDE.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Configuration

Worktree Bootstrap

Run this first in every new shell and every new worktree:

source ./init.sh

init.sh is the canonical repo bootstrap. It keeps setup simple and zero-dependency beyond the normal git + node + npm toolchain that this project already needs.

What it does:

  1. Verifies Node.js >= 18.17.
  2. Sets LGREP_HOME to .worktree/lgrep inside the current worktree so watchers, config, cache, and indexes stay isolated per worktree.
  3. Reuses a shared npm install stored under the git common directory, keyed by the lockfile, platform, architecture, and exact Node version.
  4. Uses a lock directory so multiple worktrees can bootstrap in parallel safely.
  5. Adds ./node_modules/.bin to PATH for the current shell.

Recommended flow:

source ./init.sh
npm run type-check
npm test

Prefer source ./init.sh over ./init.sh. If you execute it directly, it will prepare the environment files but cannot export variables back into your current shell.

Use lgrep for repo exploration, context building, and refactor analysis.

Core Workflow

lgrep init
lgrep doctor
lgrep list
lgrep search "authentication flow"
lgrep search --definition "UserService"
lgrep search --usages "validateUser"
lgrep callers awardBadge
lgrep impact awardBadge
lgrep context "add rate limiting"
lgrep intent "what calls awardBadge"

Storage-Aware Guidance

  • In local mode, lgrep watch can keep the current repo indexed.
  • In cloud mode, prefer the configured remote index and avoid starting local watchers unless a local workflow is explicitly requested.

Useful Commands

  • lgrep init - guided local or cloud setup
  • lgrep profile - manage named local/cloud profiles
  • lgrep doctor - diagnose setup, integration, and storage issues
  • lgrep install --target claude|codex|mcp|all - install integrations
  • lgrep config - inspect or update config values

Configuration

lgrep profile list
lgrep config
lgrep config model
lgrep config model auto
lgrep config summarizationModel auto

Read the full file on GitHub · 80 lines

Changes

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.

  1. 2mo ago First seen · 80 lines · 589 tokens per session scan A a9d21e9b5a05

Subscribe to this mod's changes

lgrep CLAUDE.md is an instructions file published in the GitHub repository dennisonbertram/lgrep (87 stars, last pushed 4mo ago), licensed MIT. It adds 589 tokens to every session, about $0.0024 per session on Opus 5.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.

Related

lgrep CLAUDE.md compared with instructions from other repositories

lgrep CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
lgrep CLAUDE.mddennisonbertram/lgrepInstructions file874mo agoMITA589Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode