Borrowing it
Nothing to install: this file belongs to vaayne/omni-fs-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/vaayne/omni-fs-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/vaayne/omni-fs-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/vaayne/omni-fs-mcp/claude-md)<a href="https://agentmods.dev/instructions/vaayne/omni-fs-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/vaayne/omni-fs-mcp/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.
<a href="https://agentmods.dev/instructions/vaayne/omni-fs-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/vaayne/omni-fs-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00414 | $0.00414 |
| Opus 5 | $0.00207 | $0.00207 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
omni-fs-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 9d 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.
What it actually says
Development Guide
Commands
# Install dependencies
uv sync
# Run tests (NOTE: No tests currently exist)
uv run pytest
# Run server locally
uv run omni-fs-mcp "memory://"
uv run omni-fs-mcp --transport http "memory://"
# Run with config
uv run omni-fs-mcp examples/demo_config.json
uv run omni-fs-mcp --transport http --config examples/demo_config.json --port 8080
# Build package
uv build
# Code quality (NOTE: No linting/formatting configured yet)
# Consider adding: ruff check src/ && ruff format src/ && mypy src/
Architecture
Core Components:
mcp_server.py- MCP server with 13 tools (7 file ops + 6 backend management)backend_manager.py- Multi-backend management with health monitoringdal.py- OpenDAL abstraction layer
Key Features:
- Multi-backend support (local, S3, WebDAV, FTP, HTTP, memory, etc.)
- Dual transport: stdio (local) and HTTP (remote)
- Backward compatible single-backend mode
- Read-only backend protection
- Runtime backend registration/removal
Testing
# Memory backend for testing
uv run omni-fs-mcp "memory://"
# Multi-backend test config
echo '{
"backends": [
{"name": "memory1", "url": "memory://", "default": true},
{"name": "memory2", "url": "memory://"}
]
}' > test_config.json
uv run omni-fs-mcp test_config.json
Development Tasks
Add Backend Types: Ensure OpenDAL supports it, test connection validation
Debug Issues: Set logging.basicConfig(level=logging.DEBUG) for detailed logs
Build System: Uses hatchling (modern PEP 517/621 compliant)
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.
- 9d ago First seen · 64 lines · 414 tokens per session scan A fba679dba467
omni-fs-mcp CLAUDE.md is an instructions file published in the GitHub repository vaayne/omni-fs-mcp (1 stars, last pushed 11mo ago), licensed MIT. It adds 414 tokens to every session, about $0.0021 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.