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/dennisonbertram/lgrep/claude-mdgit clone --depth 1 https://github.com/dennisonbertram/lgrepWrote 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/dennisonbertram/lgrep/claude-md)<a href="https://agentmods.dev/instructions/dennisonbertram/lgrep/claude-md"><img src="https://agentmods.dev/badge/instructions/dennisonbertram/lgrep/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 | $0.00589 | $0.00589 |
| Opus 5 | $0.00295 | $0.00295 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
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 4d 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 — 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:
- Verifies Node.js
>= 18.17. - Sets
LGREP_HOMEto.worktree/lgrepinside the current worktree so watchers, config, cache, and indexes stay isolated per worktree. - Reuses a shared npm install stored under the git common directory, keyed by the lockfile, platform, architecture, and exact Node version.
- Uses a lock directory so multiple worktrees can bootstrap in parallel safely.
- Adds
./node_modules/.bintoPATHfor 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.
lgrep - Semantic Code Search
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 watchcan 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 setuplgrep profile- manage named local/cloud profileslgrep doctor- diagnose setup, integration, and storage issueslgrep install --target claude|codex|mcp|all- install integrationslgrep config- inspect or update config values
Configuration
lgrep profile list
lgrep config
lgrep config model
lgrep config model auto
lgrep config summarizationModel auto
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.
- 4d ago First seen · 80 lines · 589 tokens per session scan A a9d21e9b5a05
lgrep CLAUDE.md is an instructions file published in the GitHub repository dennisonbertram/lgrep (88 stars, last pushed 2mo ago), licensed MIT. It adds 589 tokens to every session, about $0.0029 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
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.