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/linkwut-create/local-rag-core/claude-mdgit clone --depth 1 https://github.com/linkwut-create/local-rag-coreWrote 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/linkwut-create/local-rag-core/claude-md)<a href="https://agentmods.dev/instructions/linkwut-create/local-rag-core/claude-md"><img src="https://agentmods.dev/badge/instructions/linkwut-create/local-rag-core/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.00465 | $0.00465 |
| Opus 5 | $0.00233 | $0.00233 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
local-rag-core 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.
This is a copy
98% identical to local-rag-core AGENTS.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
CLAUDE.md — local-rag-core
MCP Integration
This project's knowledge base is served by its own MCP server. Before modifying any code, query the knowledge base:
kb.health — check system status and backend health
kb.list_packs — see available knowledge packs
kb.search — search across private_kb and packs
kb.get_chunk — retrieve full chunk content
Required Pre-Modification Workflow
Before proposing or implementing any code change:
-
Query project goals:
kb.search "local-rag-core project purpose and design goals" -
Check current status:
kb.health kb.list_packs -
Retrieve relevant decisions:
kb.search "<your specific topic>" -
Identify no-modify zones:
- Do NOT modify knowledge base data through MCP (read-only by design)
- Do NOT modify
storage/,data/packs/,data/private_kb/directly - Do NOT bypass the pack lifecycle (use CLI for build/export/import)
- Do NOT change the MCP tool schema without updating this file
-
Summarize retrieved context before proposing changes.
Architecture Boundaries
- MCP is read-only. All writes go through CLI (
rag ...) or HTTP API (withX-Local-RAG-Tokenauth). - Three knowledge zones:
private_kb(user's),packs(shareable),private_project(code repos with filters). - Backend status: Check
rag healthfor mock vs real backends. - Model cache: HuggingFace default at
E:\AI\huggingface\hub\. Override withLOCAL_RAG_MODEL_CACHE.
Key Commands
rag health # system health
rag pack list # registered packs
rag search "<query>" --mode hybrid # hybrid search
rag chunk get <chunk_id> # retrieve chunk
pytest && ruff check . # validate before commit
Project Status
See PROJECT_STATUS.md for current phase and capability boundaries.
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 · 66 lines · 465 tokens per session scan A 0988ef2bb600
local-rag-core CLAUDE.md is an instructions file published in the GitHub repository linkwut-create/local-rag-core (0 stars, last pushed 2mo ago), licensed MIT. It adds 465 tokens to every session, about $0.0023 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to local-rag-core AGENTS.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
pulse8-ai-cortex-knowledge-vault AGENTS.md
Instructions for synpulse8-opensource/pulse8-ai-cortex-knowledge-vault, covering agents.md — pulse8.ai cortex, repository map, environment variables, essential commands and dependencies.
mcp-documentation-server copilot-instructions.md
Instructions for andrea9293/mcp-documentation-server, covering mcp documentation server - ai coding agent instructions, architecture overview, core components, server entry point (src/server.ts) and embedding providers (src/embedding-provider.ts).
agent-brain AGENTS.md
AGENTS.md instructions for SpillwaveSolutions/agent-brain, covering agent brain agent guidelines, project overview, technology stack, package installation and build packages.
OpenDocuments AGENTS.md
Instructions for joungminsung/OpenDocuments, covering agents.md, project overview, monorepo structure, common commands and 특정 패키지만.
rag-rat AGENTS.md
Instructions for cq27-dev/rag-rat, covering agents.md, prefer the rag-rat mcp for code browsing, record durable learnings as rag-rat memories, repo orientation and worktree correctness.
James-RAG-Evol CLAUDE.md
Claude Code instructions for Hashevolution/James-RAG-Evol, covering sekos / james — session briefing for claude code, what james is, where we are right now, critical rules for this session and where to look next.