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 skills/skycaier/sky-windows-remote-executor/remote-executor-filenpx skills add skycaier/sky-windows-remote-executor --skill remote-executor-filegit clone --depth 1 https://github.com/skycaier/sky-windows-remote-executorWrote 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/skycaier/sky-windows-remote-executor/remote-executor-file)<a href="https://agentmods.dev/skills/skycaier/sky-windows-remote-executor/remote-executor-file"><img src="https://agentmods.dev/badge/skills/skycaier/sky-windows-remote-executor/remote-executor-file.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.00051 | $0.01508 |
| Opus 5 | $0.00026 | $0.00754 |
| Sonnet 5 | $0.00010 | $0.00302 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
remote-executor-file 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 3d 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 -s -X POST http://<host>:8765/file/read \ How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remote Executor 文件高级层 (v3.5)
注意: 此 skill 由关键词触发加载,不要常驻。
核心特性
- 自动编码检测:
encoding: "auto"自动识别 UTF-8 / GBK - 精准行替换:
start_line+end_line替换指定行范围 - 明确插入模式:
insert: true在指定行前插入,不替换任何行 - 自动备份:
.bak文件自动创建 - Diff 对比: 每次修改返回 unified diff(限8000字符)
- 行号读取:
include_line_numbers带行号输出
端点
读取文件(支持行范围、行号、自动编码)
POST /file/read
Content-Type: application/json
{
"path": "D:\\file.txt",
"encoding": "auto", // "auto" | "utf-8" | "gbk" | "binary"
"offset": 1, // 起始行号(1-based,0=全部)
"limit": 50, // 读取行数(0=全部)
"include_line_numbers": true // 是否带行号输出
}
返回(行范围模式):
{
"content": " 1: line1\n 2: line2...",
"encoding": "utf-8",
"total_lines": 100,
"from_line": 1,
"to_line": 50,
"truncated": false,
"include_line_numbers": true
}
写入文件(三种模式 + diff 返回)
模式1: 插入行(推荐)
POST /file/write
Content-Type: application/json
{
"path": "D:\\file.txt",
"content": "new line 1\nnew line 2\n",
"encoding": "auto", // "auto" 自动检测原文件编码
"start_line": 10, // 在第10行之前插入
"insert": true, // 明确插入模式
"backup": true // 是否自动创建 .bak 备份
}
返回:
{
"message": "插入成功 at line 10",
"path": "D:\\file.txt",
"size": 500,
"total_lines": 102,
"affected_lines": 2,
"backup": "D:\\file.txt.bak",
"mode": "insert",
"diff": "--- before\n+++ after\n@@ -8,3 +8,5 @@\n line8\n line9\n+new line 1\n+new line 2\n line10"
}
模式2: 替换行
POST /file/write
Content-Type: application/json
{
"path": "D:\\file.txt",
"content": "new line 1\nnew line 2\n",
"encoding": "auto",
"start_line": 10, // 替换起始行
"end_line": 15, // 替换结束行(0=到文件末尾)
"insert": false, // 替换模式(默认)
"backup": true
}
返回:
{
"message": "替换成功 at line 10",
"mode": "replace",
"diff": "..."
}
模式3: 传统全文件写入/追加(也返回 diff)
POST /file/write
Content-Type: application/json
{
"path": "D:\\file.txt",
"content": "全部内容",
"encoding": "auto",
"append": false, // false=覆盖写入, true=追加
"backup": true // 覆盖时自动备份原文件
}
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.
- 3d ago First seen · 180 lines · 51 tokens per session scan A 92bf80bb8275
remote-executor-file is a skill published in the GitHub repository skycaier/sky-windows-remote-executor (1 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 1,508 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…