What is lore-db CLAUDE.md?

Project instructions for Lore DB, a knowledge base that stores shared information about a software project.

Use them when developing, debugging, answering project questions, or designing features that depend on existing project context.

They require the assistant to search the knowledge base first, helping prevent guesses, repeated work, and conflicts with recorded decisions.

How andreehultgren/lore-db configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to andreehultgren/lore-db. 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/andreehultgren/lore-db/master/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/andreehultgren/lore-db

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/andreehultgren/lore-db/claude-md/github.svg)](https://agentmods.dev/instructions/andreehultgren/lore-db/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/andreehultgren/lore-db/claude-md"><img src="https://agentmods.dev/badge/instructions/andreehultgren/lore-db/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/andreehultgren/lore-db/claude-md"><img src="https://agentmods.dev/badge/instructions/andreehultgren/lore-db/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,704 This file is loaded in full into every session.

When invoked 1,704 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.

Model	Per session	Once invoked
Fable 5.1	$0.01704	$0.01704
Opus 5.5	$0.00682	$0.00682
Sonnet 5.5	$0.00341	$0.00341
Haiku 4.5	$0.00170	$0.00170

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

Security

Grade A, and why

lore-db 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 · 125 lines

How it starts

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

Instructions for Lore DB

General Instructions

Any new feature starts with unit tests. These tests must be verified before work starts. Then we iterate against the tests to ensure that we are building a robust product.

Knowledge Base Protocol (The "Brain")

The knowledge-base MCP is our Living Source of Truth and the primary source for all project knowledge. You are its caretaker.

CRITICAL RULE: Search the knowledge base FIRST, before every task. Do not rely on your training data, memory, or assumptions about this project. The KB contains project-specific decisions, patterns, conventions, and context that override general knowledge. If you skip this step, you risk contradicting established decisions or duplicating solved problems.

When to Search (Always)

You MUST search the knowledge base at the start of every task, including but not limited to:

Before writing or modifying code — search for relevant architecture decisions, patterns, or conventions
Before answering questions about the project — the KB may already have the answer
Before debugging — search for known issues, past fixes, or related context
Before designing a feature — search for prior design decisions or constraints
Before refactoring — search for documented reasons behind the current structure
When encountering unfamiliar code — search for explanations or context

Run multiple searches with different queries if your first search doesn't cover the full scope of the task. Cast a wide net — it's better to search too much than too little.

Available MCP Tools

Tool	When to use
`search_documents(query, limit)`	Find relevant documents by meaning
`get_document(document_id)`	Fetch full content of a specific document
`create_document(title, content)`	Add a new Brief
`update_document(document_id, title, content)`	Update an existing Brief
`delete_document(document_id)`	Remove a stale Brief
`verify_document(document_id)`	Confirm a document is still accurate (bumps freshness)
`get_stale_documents(days_threshold)`	Find documents that may be outdated
`reindex_documents()`	Re-embed all documents after embedder changes

Read the full file on GitHub · 125 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.

2mo ago First seen · 125 lines · 1,704 tokens per session scan A 09f45ede8c9f

Subscribe to this mod's changes

lore-db CLAUDE.md is an instructions file published in the GitHub repository andreehultgren/lore-db (0 stars, last pushed 8mo ago), licensed MIT. It adds 1,704 tokens to every session, about $0.0068 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.

Memory and context

lore-db CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
lore-db CLAUDE.mdandreehultgren/lore-db	Instructions file	0	8mo ago	MIT	A	1,704	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

lore-db: Instructions file for Claude Code