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/agents-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/agents-md)<a href="https://agentmods.dev/instructions/linkwut-create/local-rag-core/agents-md"><img src="https://agentmods.dev/badge/instructions/linkwut-create/local-rag-core/agents-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.00464 | $0.00464 |
| Opus 5 | $0.00232 | $0.00232 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
local-rag-core AGENTS.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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- local-rag-core CLAUDE.md — 98% identical, 2 lines differ
What it actually says
AGENTS.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.
- 3d ago First seen · 66 lines · 464 tokens per session scan A df1fe573db72
local-rag-core AGENTS.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 464 tokens to every session, about $0.0023 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
knowledge-base-system-oss AGENTS.md
AGENTS.md instructions for Snorlax-zzZ/knowledge-base-system-oss, covering knowledge-base-system 规则说明, 1. 适用范围, 2. 产品契约(必须遵守), 3. 跨平台一致性规则(重要) and 4. 分层边界.
siyuan AGENTS.md
AGENTS.md instructions for siyuan-note/siyuan, covering agents.md, 1. non-negotiable constraints, do not hand-edit, verification and prohibited operations and 2. project-specific rules.
stashbase AGENTS.md
AGENTS.md instructions for liliu-z/stashbase, covering agent maintenance contract for this repo, github access for this repository, temporary worktrees, electron launch environment and documentation route.
Starcat AGENTS.md
AGENTS.md instructions for starcat-app/Starcat, covering agents.md, 🚨 硬性铁律(每次写代码前必读,违反即返工), 🌿 git 分支与 worktree(强制), 🧭 主进度索引(每次开工前必读) and 状态符号(与功能实现总览.md 同步).
llm-wiki-newsroom AGENTS.md
Instructions for alfadur7/llm-wiki-newsroom, covering llm wiki newsroom — schema & workflow instructions, how to use, directory layout, page format and ingest workflow.
llm-wiki-newsroom GEMINI.md
Instructions for alfadur7/llm-wiki-newsroom, covering llm wiki newsroom — schema & workflow instructions, how to use, directory layout, page format and ingest workflow.