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/mocchalera/xserver-files-mcp/agents-mdgit clone --depth 1 https://github.com/mocchalera/xserver-files-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/mocchalera/xserver-files-mcp/agents-md)<a href="https://agentmods.dev/instructions/mocchalera/xserver-files-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/mocchalera/xserver-files-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 | $0.00404 | $0.00404 |
| Opus 5 | $0.00202 | $0.00202 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
xserver-files-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 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.
What it actually says
AGENTS.md
Scope
- Maintain the local stdio MCP server and CLI for XServer SFTP file operations in this repository.
- Keep repository guidance concise; detailed operating workflows belong in
skills/xserver-files-operator/SKILL.mdandskills/xserver-mcp-operator/SKILL.md.
Required Commands
- Setup:
npm install - Test:
npm test - CLI smoke check:
XSERVER_FILES_CONFIG=config/example.config.json node src/cli.js servers
Hard Constraints
- Do not commit private keys, passphrases, server passwords, or real local config files.
- Do not hard-code live XServer credentials in source code or tests.
- Keep file operations constrained to configured
roots[domain]; never add absolute remote-path inputs to tools. - Preserve write safety: existing remote files must be backed up by default.
Task Workflow
- Prefer shared operation code in
src/operations.js; keepsrc/server.jsandsrc/cli.jsas thin adapters. - Use
skills/as the authored project-skill source;.claude/skills/,.agents/skills/,.gemini/skills/,.cursor/skills/,.grok/skills/, and.antigravity/skills/are compatibility views. - Keep XServer-provided MCP guidance separate from the custom SFTP MCP/CLI guidance.
- Run
npm run validate:agent-supportafter changing skills or agent-facing entrypoints. - Before changing remote-write behavior, update or add tests that exercise dry-run, backup, and path-safety behavior.
Definition of Done
npm testpasses.npm run validate:agent-supportpasses when skills or agent-facing entrypoints change.- MCP stdio smoke coverage still lists and calls at least one read-only tool.
- README and project skills stay aligned with any command, config, or XServer MCP workflow changes.
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 · 30 lines · 404 tokens per session scan A f8c6305363fe
xserver-files-mcp AGENTS.md is an instructions file published in the GitHub repository mocchalera/xserver-files-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 404 tokens to every session, about $0.0020 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.
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.