Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/skills/mocchalera/xserver-files-mcp/xserver-files-operator)<a href="https://agentmods.dev/skills/mocchalera/xserver-files-mcp/xserver-files-operator"><img src="https://agentmods.dev/badge/skills/mocchalera/xserver-files-mcp/xserver-files-operator.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.00064 | $0.01033 |
| Opus 5 | $0.00032 | $0.00517 |
| Sonnet 5 | $0.00013 | $0.00207 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
xserver-files-operator scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -I http://old-site.example.com/ How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XServer Files Operator
Overview
Use this skill to work with the local MCP/CLI in this repository without bypassing its safety model. The MCP connects to XServer over SFTP on port 10022, restricts paths to configured domain roots, and backs up existing files before writes by default.
Safety Contract
- Treat
~/.config/xserver-files-mcp/config.jsonas the operator-owned config; keep onlyconfig/example.config.jsonin the repo. - Keep private keys under
~/.ssh/, not in this repository. - Use
server_idfor multi-server work; omit it only when the default server is intended. - Use configured domains such as
old-site.example.com; do not pass absolute remote paths to tools or CLI commands. - Run dry-run first for redirect and write workflows unless the user explicitly asks for an immediate write.
- Keep backups enabled unless the user explicitly accepts the risk.
- Keep local site workspaces outside this repository, normally under
~/Dev/xserver-sites. - Use workspace pull/push for edited site files; do not clone WordPress/site trees into this tool repository.
- Treat
wp-config.php, uploads, logs, backups, SQL/database dumps, and archives as default-excluded workspace paths unless the user explicitly accepts the risk. - Understand that
replaceInFileandset_domain_redirectare not atomic: they read, transform, and write in separate SFTP calls. If another operator edits the same file concurrently, their changes may be lost. Coordinate access or use pull/push workflow for critical edits.
Local Checks
Install and test:
npm install
npm test
Check config parsing without connecting to XServer:
XSERVER_FILES_CONFIG=config/example.config.json node src/cli.js servers
Create a domain workspace outside the repository:
node src/cli.js workspace old-site.example.com
Pull one file for local editing:
node src/cli.js pull old-site.example.com .htaccess
Push the matching workspace file back with a dry-run first:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 129 lines · 64 tokens per session scan A 7b1dfed83197
xserver-files-operator is a skill published in the GitHub repository mocchalera/xserver-files-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 1,033 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…