Borrowing it
Nothing to install: this file belongs to VXConsulting/claude-rag-mcp. 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/VXConsulting/claude-rag-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/VXConsulting/claude-rag-mcpWrote 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/vxconsulting/claude-rag-mcp/claude-md)<a href="https://agentmods.dev/instructions/vxconsulting/claude-rag-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/vxconsulting/claude-rag-mcp/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.00602 | $0.00602 |
| Opus 5 | $0.00301 | $0.00301 |
| Sonnet 5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
claude-rag-mcp 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 7d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Last Updated: 2026-02-02 (v1.0.0 - Initial Release)
Project Overview
Repository: /home/olivier/dev/claude-rag-mcp
Branch: main
Version: 1.0.0
Purpose: MCP server providing RAG context and failure capture for Claude Code
Architecture
MCP Server (src/mcp/server.ts)
↓
┌─────────────────────────────────────────────────────┐
│ Context (RAG) │
│ src/context/ - semantic search, knowledge store │
│ Providers: memory, chromadb │
└─────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────┐
│ Learning (Capture) │
│ src/learning/ - failure storage (SQLite) │
│ Types: test, review, quality_gate, timeout, error │
└─────────────────────────────────────────────────────┘
MCP Tools (11 total)
- Context (7):
context_status,context_search,context_list,context_get,context_add,context_delete,context_prune - Learning (4):
learning_status,learning_list_failures,learning_get_failure,learning_prune
Technical Stack
- Language: TypeScript 5.7 (strict mode) with NodeNext module resolution
- Module System: ESM (
"type": "module") - Testing: Vitest 4.0 with colocated
__tests__/directories - MCP: @modelcontextprotocol/sdk 1.0
Key Files
src/mcp/server.ts- MCP server with 11 toolssrc/mcp/context-tools.ts- 7 RAG toolssrc/mcp/learning-tools.ts- 4 failure capture toolssrc/context/- Global context module (RAG system)src/learning/- Failure capture servicesrc/cli.ts- CLI entry point (serve command)src/config/config-loader.ts- YAML config loader
Commands
npm run build # Compile TypeScript
npm test # Run all tests
npm run test:watch # Watch mode
npm run serve # Start MCP server
Conventions
- ESM with NodeNext module resolution
- Strict TypeScript throughout
- Tests colocated in
__tests__/directories - Use
import { randomUUID } from 'node:crypto'(Node 18+) - Zod for config validation with
safeParse
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.
- 7d ago First seen · 72 lines · 602 tokens per session scan A 082ded700b14
claude-rag-mcp CLAUDE.md is an instructions file published in the GitHub repository VXConsulting/claude-rag-mcp (1 stars, last pushed 7mo ago), licensed MIT. It adds 602 tokens to every session, about $0.0030 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.