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 skills add skycaier/sky-windows-remote-executor --skill remote-executor-networkgit 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-network)<a href="https://agentmods.dev/skills/skycaier/sky-windows-remote-executor/remote-executor-network"><img src="https://agentmods.dev/badge/skills/skycaier/sky-windows-remote-executor/remote-executor-network/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/skycaier/sky-windows-remote-executor/remote-executor-network"><img src="https://agentmods.dev/badge/skills/skycaier/sky-windows-remote-executor/remote-executor-network.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.00679 |
| Opus 5.5 | $0.00011 | $0.00272 |
| Sonnet 5.5 | $0.00005 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
remote-executor-network 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 2mo 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.
trigger_keywords: ["ping", "端口", "port", "网络", "network", "连接", "connection", "抓取", "scrape", "网页", "curl"] What it actually says
Remote Executor 网络层 (v3.5)
注意: 此 skill 由关键词触发加载,不要常驻。
端点
网页抓取
POST /net/scrape
Content-Type: application/json
{"url": "https://example.com"}
返回:
{"url": "https://example.com", "content": "HTML内容...", "size": 5000, "truncated": false}
- 限制 1MB,返回内容限制 50KB
Ping
POST /net/ping
Content-Type: application/json
{
"host": "192.168.1.1",
"count": 4
}
返回:
{"host": "192.168.1.1", "count": 4, "output": "...", "returncode": 0}
端口检测
POST /net/port-check
Content-Type: application/json
{
"host": "<host>",
"port": 8765,
"timeout": 5.0
}
返回:
{"host": "<host>", "port": 8765, "open": true, "code": 0}
网络连接
POST /net/connections
Content-Type: application/json
{
"filter": "8765", // 可选过滤
"limit": 50
}
返回:
{
"connections": [
{"local": "0.0.0.0:8765", "remote": "0.0.0.0:0", "state": "Listen", "pid": 1234}
],
"count": 1
}
使用示例
Ping 测试:
curl -s -X POST http://<host>:8765/net/ping \
-H "Content-Type: application/json" \
-d '{"host": "baidu.com", "count": 4}'
检测端口:
curl -s -X POST http://<host>:8765/net/port-check \
-H "Content-Type: application/json" \
-d '{"host": "<host>", "port": 8765}'
抓取网页:
curl -s -X POST http://<host>:8765/net/scrape \
-H "Content-Type: application/json" \
-d '{"url": "https://www.baidu.com"}'
查看网络连接:
curl -s -X POST http://<host>:8765/net/connections \
-H "Content-Type: application/json" \
-d '{"filter": "", "limit": 20}'
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.
- 2mo ago First seen · 105 lines · 27 tokens per session scan A 84e983528fe5
remote-executor-network is a skill published in the GitHub repository skycaier/sky-windows-remote-executor (1 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 679 once invoked, about $0.0001 per session on Opus 5.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
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
chrome-performance-optimizer
Autonomous multi-agent performance optimization loop for Chromium and V8. Supports profile-seeded mode (analyzing Speedometer 3 / JetStream profiles via pprof or Sagacity MCP) and pattern-driven discovery mode (fan-out exploration of Blink and V8 macro-patterns grounded in historical wins and past rejected CLs).…
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
nullaway
Guide for resolving NullAway static analysis errors. Best practices for: Passing ObservableSupplier/Supplier Dereferencing potentially @Nullable values Adding @NullMarked to Java code.
reenable-test
Guide for investigating, fixing, verifying via TDD, and re-enabling disabled or flaky Chromium tests (C++, Android Java, or WebUI). Use this skill when asked to deflake, fix, or re-enable a disabled or flaky test case, or to verify post-submit stability of a re-enabled test. Don't use for disabling a failing test…
bisect
Bisect regressions or broken builds in the Chromium repository using deterministic binary search, checking out midpoint commits, syncing dependencies with gclient sync, compiling the target with autoninja, and querying the user for test results until the culprit commit is isolated.