Borrowing it
Nothing to install: this file belongs to jafreck/Lore. 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/jafreck/Lore/main/CLAUDE.mdgit clone --depth 1 https://github.com/jafreck/LoreWrote 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/jafreck/lore/claude-md)<a href="https://agentmods.dev/instructions/jafreck/lore/claude-md"><img src="https://agentmods.dev/badge/instructions/jafreck/lore/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/jafreck/lore/claude-md"><img src="https://agentmods.dev/badge/instructions/jafreck/lore/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.00611 | $0.00611 |
| Opus 5.5 | $0.00244 | $0.00244 |
| Sonnet 5.5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
Lore 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 1mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project
Lore is a pre-release code-intelligence service. It stores recognized source snapshots and SCIP/LSP-derived facts in SQLite, can add Git history and vector embeddings, and serves the effective index through 11 MCP tools. It has no tree-sitter extraction path, documentation corpus, dependency crawler, or active complexity-metrics producer.
Architecture invariants
- The active stage order is
ScipIndexerStage→FileDiscoveryStage→LspExtractionStage→ImportResolutionStage→ [LspEnrichmentStage+git-history] →symbol-resolution→ReverseDepsStage→EmbeddingStage→FtsRefreshStage. - Baseline validation and generation promotion occur after the stage pipeline. Promotion is not an active pipeline stage.
- SCIP is the primary baseline structural source and does not run for overlay updates. LSP extracts changed-file overlays.
- Baseline LSP supplementation selects every non-SCIP-sourced file and
SCIP-sourced C/C++ files with no symbols or repairable spans. It is bounded by
supplementation.maxFilesandfileConcurrency; strict mode fails rather than truncating the plan. - Schema v3 uses branch-scoped promoted generations, dirty-file selectors,
persistent
effective_*views, and connection-local staging views. Keep candidate generations hidden until validation succeeds. - Public query paths use effective state. When overlays replace targets, reconcile stored file IDs and requeue symbol targets before resolution.
- Repository
.lore.configvalues are requests, never execution authority. Host grants must remain separate and explicit.
Change policy
Lore may make clean breaking changes before 1.0. Remove dead implementations instead of maintaining parallel APIs, and prefer the smallest complete design.
The current schema contract is different from a compatibility shim: writable
opens must apply the declared ordered migrations [1, 2, 3], both schema
markers must be present and agree, and read-only consumers must reject
incompatible databases.
Any schema change must deliberately update the version, migration sequence,
capability inspection, and tests. Do not remove required migration behavior
merely because the product is pre-release.
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.
- 1mo ago Changed · +20 lines · -161 tokens per session 1c1abdc9a5ef
- 1mo ago Changed · +1 lines · +82 tokens per session 5197e07e8a67
- 2mo ago First seen · 46 lines · 690 tokens per session scan A 3b8e2a3bd6f4
Lore CLAUDE.md is an instructions file published in the GitHub repository jafreck/Lore (7 stars, last pushed 1mo ago), licensed MIT. It adds 611 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-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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.