What is RAGBuddy CLAUDE.md?

Repository instructions for RAGBuddy, a project that uses an MCP server to retrieve information from project documentation. MCP lets an agent use connected tools.

Loading the right skill, reading documentation, tracing code, adding tests when useful, and updating docs for changes.

They require developers to follow the project’s documented workflow before changing code.

How azmirizkifar20/RAGBuddy configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to azmirizkifar20/RAGBuddy. 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/azmirizkifar20/RAGBuddy/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/azmirizkifar20/RAGBuddy

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/azmirizkifar20/ragbuddy/claude-md/github.svg)](https://agentmods.dev/instructions/azmirizkifar20/ragbuddy/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/azmirizkifar20/ragbuddy/claude-md"><img src="https://agentmods.dev/badge/instructions/azmirizkifar20/ragbuddy/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/azmirizkifar20/ragbuddy/claude-md"><img src="https://agentmods.dev/badge/instructions/azmirizkifar20/ragbuddy/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 517 This file is loaded in full into every session.

When invoked 517 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 100% copy Near-identical to another mod 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.00517	$0.00517
Opus 5	$0.00259	$0.00259
Sonnet 5	$0.00103	$0.00103
Haiku 4.5	$0.00052	$0.00052

Measured 8d ago against content hash 1fbbf48ba820, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

RAGBuddy 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 8d 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.

Origin

This is a copy

100% identical to RAGBuddy AGENTS.md — 0 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.

CLAUDE.md · 31 lines

How it starts

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

Skills Auto-Load

Before implementing any feature, change, extension, or refactoring task, ALWAYS check and load the appropriate skill:

For feature work (implement, add, create, change, extend, refactor): Load ragbuddy-feature-flow skill first
The skill defines the required workflow: read docs → trace runtime path → add/update tests when they protect the change → verify → update/create docs

When the user asks for any code change (implement, add, fix, refactor), ALWAYS load ragbuddy-feature-flow before touching code — regardless of task size.

Documentation Structure

This project uses structured documentation under docs/:

docs/features/ - Current-state (and planned) feature documentation
docs/steering/ - Technical architecture and stack decisions
docs/issue/ - Bug reports and root cause analysis
docs/design-system/ - Tokens, motion and component conventions for the web/ dashboard (Vite + React + Tailwind + shadcn/ui). It is a small internal tool, so this records the conventions it follows rather than prescribing a component library.

Knowledge Retrieval Strategy (ragbuddy MCP)

Before implementing a non-trivial feature in this project:

Use get_project_context first to understand the project (identity, Git status, tech stack/architecture summaries, doc inventory).
Use search_project_docs for architecture, business rules, historical issues, conventions, and documented behavior.
Use get_project_document to read a full doc found via search when a snippet isn't enough.
Use list_project_knowledge to see everything currently indexed when orienting from scratch.
Read the actual source code before making implementation decisions — treat it as the final authority for current behavior.

Don't force get_project_context for trivial tasks where it adds no value.

Project Status

RAGBuddy is fully implemented: all six phases from init.md §26 (Foundation, Full Ingestion, Incremental Sync, Retrieval, MCP Server, Git Hook Auto Sync) plus the web frontend + CLI project subcommands (docs/features/07-web-frontend-and-project-cli.md) and the dashboard redesign with document uploads and sync history (docs/features/08-dashboard-redesign-uploads-and-history.md). docs/features/*.md describe shipped, current-state behavior — see docs/features/README.md for the full index.

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

8d ago First seen · 31 lines · 517 tokens per session scan A 1fbbf48ba820

Subscribe to this mod's changes

RAGBuddy CLAUDE.md is an instructions file published in the GitHub repository azmirizkifar20/RAGBuddy (0 stars, last pushed 18d ago), licensed MIT. It adds 517 tokens to every session, about $0.0026 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to RAGBuddy AGENTS.md, differing in 0 lines, and is treated as a copy.

Data and AI RAG and vectors ai-chat mcp mcp-server mcp-tools rag-pipeline

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

RAGBuddy: Instructions file for Claude Code