Borrowing it
Nothing to install: this file belongs to evoleinik/claude-grep. 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/evoleinik/claude-grep/main/CLAUDE.mdgit clone --depth 1 https://github.com/evoleinik/claude-grepWrote 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/evoleinik/claude-grep/claude-md)<a href="https://agentmods.dev/instructions/evoleinik/claude-grep/claude-md"><img src="https://agentmods.dev/badge/instructions/evoleinik/claude-grep/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.
<a href="https://agentmods.dev/instructions/evoleinik/claude-grep/claude-md"><img src="https://agentmods.dev/badge/instructions/evoleinik/claude-grep/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.01971 | $0.01971 |
| Opus 5.5 | $0.00788 | $0.00788 |
| Sonnet 5.5 | $0.00394 | $0.00394 |
| Haiku 4.5 | $0.00197 | $0.00197 |
Grade A, and why
claude-grep 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 27d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-grep
Search Claude Code session history.
Quick reference
claude-grep "pattern" # regex search
claude-grep -s "meaning query" # semantic search
claude-grep --json "x" | jq . # JSON output
claude-grep -p -C 2 "error" # prompts only, with context
claude-grep -a -d 30 "deploy" # all projects, 30 days
claude-grep --index # build/update index
claude-grep --index --status # index stats
Build
go build -o claude-grep .
go install .
go vet ./...
scripts/coverage.sh # all tests + total coverage; exit 1 under 80%. CI runs this
Tests
*_test.gobeside each file are unit tests.e2e*_test.gobuild the real binary and drive it in a sandbox (newSandbox): temp$HOME, fixture transcripts, fake ollama. A new flag, subcommand or exit path gets an e2e case, becausemain()and therun*entry points callos.Exitand cannot be reached from a unit test.- Fixture transcripts get an hour-old mtime (
sandbox.session). The search skips the newest file when it is under 60s old, so a just-written fixture silently vanishes. - The bench drops any project whose name contains
claude-grep. Bench fixtures use their own project name, never one derived from the temp dir. - Coverage of the child binary reaches the profile because
go test -coversetsGOCOVERDIRfor the test process; the harness builds the child with-cover. - CI uploads to Codecov over OIDC with
fail_ci_if_error: true. It wasfalse, and every upload was rejected for seven months while CI stayed green.
Architecture
| File | Purpose |
|---|---|
main.go |
CLI flags, routing |
search.go |
JSONL parsing, regex search, concurrent file processing |
bm25.go |
BM25 query-focused paragraph compression |
format.go |
Terminal (colored) and JSON output |
index.go |
Ollama embedding, incremental indexer |
store.go |
Gob-based vector store on disk |
vector.go |
Cosine similarity, semantic search |
bench.go |
Session recovery bench: rank scoring + regex-baseline gate |
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.
- 27d ago Changed · +16 lines · +269 tokens per session ed06c50e7b79
- 1mo ago Changed · +81 lines · +1,053 tokens per session ac4f19082b88
- 2mo ago First seen · 65 lines · 649 tokens per session scan A 9b37e16f33ec
claude-grep CLAUDE.md is an instructions file published in the GitHub repository evoleinik/claude-grep (2 stars, last pushed 27d ago), licensed MIT. It adds 1,971 tokens to every session, about $0.0079 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-31.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.