Borrowing it
Nothing to install: this file belongs to Venere-Labs/ragfs. 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/Venere-Labs/ragfs/main/CLAUDE.mdgit clone --depth 1 https://github.com/Venere-Labs/ragfsWrote 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/venere-labs/ragfs/claude-md)<a href="https://agentmods.dev/instructions/venere-labs/ragfs/claude-md"><img src="https://agentmods.dev/badge/instructions/venere-labs/ragfs/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.01101 | $0.01101 |
| Opus 5 | $0.00550 | $0.00550 |
| Sonnet 5 | $0.00220 | $0.00220 |
| Haiku 4.5 | $0.00110 | $0.00110 |
Grade A, and why
ragfs 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 6d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Build Commands
cargo build # Development build
cargo build --release # Release build
cargo build -p <crate-name> # Build specific crate
Testing
cargo test --all # Run all tests
cargo test -p <crate-name> # Run tests for specific crate
cargo test -- --nocapture # Run tests with output
Linting & Formatting
cargo fmt --all # Format code
cargo fmt --all -- --check # Check formatting
cargo clippy --all-targets -- -D warnings # Run clippy
Running
cargo run -- -v index /path/to/dir # Index with verbose logging
cargo run -- query /path "search" # Query the index
RUST_LOG=debug cargo run -- ... # Debug logging
Architecture
RAGFS is a FUSE filesystem for semantic search using vector embeddings. It's organized as a Rust workspace with 9 crates following a pipeline pattern:
File → Extraction → Chunking → Embedding → Storage → Search
Crate hierarchy:
ragfs- CLI binary (entry:crates/ragfs/src/main.rs)ragfs-core- Foundation traits and types (traits.rs,types.rs)ragfs-extract- Content extraction viaExtractorRegistryragfs-chunker- Document chunking viaChunkerRegistryragfs-embed- Local embeddings using Candle (gte-small, 384-dim)ragfs-store- Vector storage with LanceDBragfs-index- Pipeline orchestration and file watchingragfs-query- Query executionragfs-fuse- FUSE filesystem with agent operations, safety layer, and semantic features
ragfs-fuse modules:
filesystem.rs- Main FUSE handler, inode management, virtual directory routingops.rs-OpsManagerfor file operations with JSON feedback (.ops/)safety.rs-SafetyManagerfor soft delete, audit logging, undo (.safety/)semantic.rs-SemanticManagerfor AI-powered file operations (.semantic/)
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.
- 6d ago First seen · 115 lines · 1,101 tokens per session scan A f8322aebedc9
ragfs CLAUDE.md is an instructions file published in the GitHub repository Venere-Labs/ragfs (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 1,101 tokens to every session, about $0.0055 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-30.
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.