Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/jeswin/mcpfs/claude-mdgit clone --depth 1 https://github.com/jeswin/mcpfsWrote 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/jeswin/mcpfs/claude-md)<a href="https://agentmods.dev/instructions/jeswin/mcpfs/claude-md"><img src="https://agentmods.dev/badge/instructions/jeswin/mcpfs/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 | $0.00960 | $0.00960 |
| Opus 5 | $0.00480 | $0.00480 |
| Sonnet 5 | $0.00192 | $0.00192 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
mcpfs 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 4d 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 — 132 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 when working with the mcpfs codebase.
Critical Guidelines
NEVER ACT WITHOUT EXPLICIT USER APPROVAL
YOU MUST ALWAYS ASK FOR PERMISSION BEFORE:
- Making architectural decisions or changes
- Implementing new features or functionality
- Modifying APIs, interfaces, or data structures
- Changing expected behavior or test expectations
- Adding new dependencies or patterns
ONLY make changes AFTER the user explicitly approves. When you identify issues or potential improvements, explain them clearly and wait for the user's decision. Do NOT assume what the user wants or make "helpful" changes without permission.
FINISH DISCUSSIONS BEFORE WRITING CODE
IMPORTANT: When the user asks a question or you're in the middle of a discussion, DO NOT jump to writing code. Always:
- Complete the discussion first - Understand the problem fully
- Analyze and explain - Work through the issue verbally
- Get confirmation - Ensure the user agrees with the approach
- Only then write code - After the user explicitly asks you to implement
Project Overview
mcpfs is an HTTP streaming port of the official MCP Filesystem Server. It replaces stdio transport with HTTP Streaming (Streamable HTTP transport) for remote access and web client compatibility.
Key Features
- Read/write files
- Create/list/delete directories
- Move files/directories
- Search files
- Get file metadata
- Dynamic directory access control via MCP Roots
- OAuth 2.1 authentication with PKCE support
- ChatGPT integration via MCP connectors
Code Principles
- NO CLASSES - Use functional style with strict types
- PREFER
typeoverinterface - USE RESULT TYPES - For error handling where appropriate
- ESM MODULES - All imports must include
.jsextension
Linting and Code Quality Standards
CRITICAL: NEVER weaken linting, testing, or type-checking rules:
- NO eslint-disable comments - Fix the actual issues instead of suppressing warnings
- NO @ts-expect-error or @ts-ignore - Fix type errors properly
- NO relaxing TypeScript strict mode - Maintain full type safety
- NO weakening any quality gates - Standards exist for a reason
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.
- 4d ago First seen · 132 lines · 960 tokens per session scan A 5964cf17f2f4
mcpfs CLAUDE.md is an instructions file published in the GitHub repository jeswin/mcpfs (0 stars, last pushed 8mo ago), licensed MIT. It adds 960 tokens to every session, about $0.0048 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.