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/andreehultgren/lore-db/claude-mdgit clone --depth 1 https://github.com/andreehultgren/lore-dbWrote 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/andreehultgren/lore-db/claude-md)<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="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.1 | $0.01704 | $0.01704 |
| Opus 5 | $0.00852 | $0.00852 |
| Sonnet 5 | $0.00341 | $0.00341 |
| Haiku 4.5 | $0.00170 | $0.00170 |
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 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 — 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 |
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 · 125 lines · 1,704 tokens per session scan A 09f45ede8c9f
lore-db CLAUDE.md is an instructions file published in the GitHub repository andreehultgren/lore-db (0 stars, last pushed 5mo ago), licensed MIT. It adds 1,704 tokens to every session, about $0.0085 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-31.
Other instructions, from other repositories
aeon CLAUDE.md
Claude Code instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
cognirepo CLAUDE.md
Claude Code instructions for ashlesh-t/cognirepo, covering claude.md, key rules, session start sequence (run in this order), behavioral confirmation rule and personas (cognirepo-402, cognirepo-403).
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
memory-mcp-1file AGENTS.md
Instructions for pomazanbohdan/memory-mcp-1file, covering ⛔ l0 invariants (never violate under any circumstance), detection heuristic, 🔀 phase transition routing (⛔ blocking), gate-0: phase identification & loading and 🧾 proof-of-load requirement (critical).