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.
curl -O https://raw.githubusercontent.com/azmirizkifar20/RAGBuddy/main/AGENTS.mdgit clone --depth 1 https://github.com/azmirizkifar20/RAGBuddyWrote 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/azmirizkifar20/ragbuddy/agents-md)<a href="https://agentmods.dev/instructions/azmirizkifar20/ragbuddy/agents-md"><img src="https://agentmods.dev/badge/instructions/azmirizkifar20/ragbuddy/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.1 | $0.00517 | $0.00517 |
| Opus 5 | $0.00259 | $0.00259 |
| Sonnet 5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
RAGBuddy 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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- RAGBuddy CLAUDE.md — 100% identical, 0 lines differ
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-flowskill 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 documentationdocs/steering/- Technical architecture and stack decisionsdocs/issue/- Bug reports and root cause analysisdocs/design-system/- Tokens, motion and component conventions for theweb/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_contextfirst to understand the project (identity, Git status, tech stack/architecture summaries, doc inventory). - Use
search_project_docsfor architecture, business rules, historical issues, conventions, and documented behavior. - Use
get_project_documentto read a full doc found via search when a snippet isn't enough. - Use
list_project_knowledgeto 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.
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 · 31 lines · 517 tokens per session scan A 1fbbf48ba820
RAGBuddy AGENTS.md is an instructions file published in the GitHub repository azmirizkifar20/RAGBuddy (0 stars, last pushed 17d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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.
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).
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).
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.
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.