Borrowing it
Nothing to install: this file belongs to SylphxAI/filesystem-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/SylphxAI/filesystem-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/SylphxAI/filesystem-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/sylphxai/filesystem-mcp/agents-md)<a href="https://agentmods.dev/instructions/sylphxai/filesystem-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/sylphxai/filesystem-mcp/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.00455 | $0.00455 |
| Opus 5 | $0.00228 | $0.00228 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
filesystem-mcp 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
filesystem-mcp — local agent notes only
Static engineering and delivery standards load from the active Skills runtime (SylphxAI/skills is binding instruction SSOT). Doctrine and Mission Control are retired historical lineage and must not be loaded as current instruction authority.
Local truth: PROJECT.md, .doctrine/project.json when present.
Boundary hazards
- This is a security-sensitive MCP filesystem server. Path confinement, batch
- Release workflows publish npm, Docker Hub images, GitHub releases, and docs.
- Do not mix package/image publishing changes with docs/control-plane changes.
Local commands
pnpm install --frozen-lockfile- install dependencies.pnpm run validate- formatting, lint, typecheck, and tests.pnpm run build- build package artifacts.pnpm run docs:build- build documentation.- Prefer the narrowest affected check before full workspace runs.
- Report layers honestly: local diff · trunk FF · deploy · prod proof (do not collapse).
Validation notes
- Prefer the narrowest affected check before full workspace runs.
- Report layers honestly: local diff · trunk FF · deploy · prod proof (do not collapse).
Backend false-authority fence
Work: wi_01KYFN6993PMG8WD00Q51AE231
If this repository has completed a Rust backend cutover:
- Production backend behavior authority is the Rust crate/binary/service path declared in
sylphx.toml/ deploy manifests / packagebinnative path / Docker ENTRYPOINT. - Residual TypeScript service trees or alternate TS engines are not product authority unless explicitly proven still on the live path.
- Do not "fix production" by editing residual TypeScript and assuming deploy/runtime will pick it up.
- Prefer deleting residual TS backend trees after Rust sole proof; keep history in Git.
- Intentional TypeScript frontends, npm packaging wrappers, and native-binding surfaces may remain.
Repo-specific note
Rust binary is runtime authority; TS/npm packaging is not an alternate backend implementation.
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 · 45 lines · 455 tokens per session scan A f063819ef83d
filesystem-mcp AGENTS.md is an instructions file published in the GitHub repository SylphxAI/filesystem-mcp (8 stars, last pushed 1mo ago), licensed MIT. It adds 455 tokens to every session, about $0.0023 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
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).
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.
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).
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.