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-desktopnpx skills add skycaier/sky-windows-remote-executor --skill remote-executor-desktopgit 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-desktop)<a href="https://agentmods.dev/skills/skycaier/sky-windows-remote-executor/remote-executor-desktop"><img src="https://agentmods.dev/badge/skills/skycaier/sky-windows-remote-executor/remote-executor-desktop.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.00030 | $0.00598 |
| Opus 5 | $0.00015 | $0.00299 |
| Sonnet 5 | $0.00006 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
remote-executor-desktop 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 http://<host>:8765/clipboard What it actually says
Remote Executor 桌面层 (v3.5)
注意: 此 skill 由关键词触发加载,不要常驻。
端点
剪贴板
读取剪贴板
GET /clipboard
返回:
{"content": "剪贴板内容"}
设置剪贴板
POST /clipboard
Content-Type: application/json
{"text": "要设置的内容"}
通知
发送 Windows 通知
POST /notification
Content-Type: application/json
{
"title": "Remote Executor",
"message": "任务已完成!"
}
锁屏
锁定工作站
POST /lock-screen
返回:
{"message": "Screen locked"}
事件日志
查询 Windows 事件日志
POST /event-log
Content-Type: application/json
{
"log_name": "System", // System, Application, Security
"count": 20,
"level": "error" // critical, error, warning, information, verbose
}
返回:
{
"events": [
{"time": "2024-01-01T00:00:00", "id": 1000, "level": "Error", "provider": "Service", "message": "..."}
],
"count": 1,
"log_name": "System"
}
使用示例
读取剪贴板:
curl -s http://<host>:8765/clipboard
设置剪贴板:
curl -s -X POST http://<host>:8765/clipboard \
-H "Content-Type: application/json" \
-d '{"text": "Hello from Remote Executor"}'
发送通知:
curl -s -X POST http://<host>:8765/notification \
-H "Content-Type: application/json" \
-d '{"title": "测试", "message": "这是一条测试通知"}'
查询系统错误日志:
curl -s -X POST http://<host>:8765/event-log \
-H "Content-Type: application/json" \
-d '{"log_name": "System", "count": 10, "level": "error"}'
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 · 106 lines · 30 tokens per session scan A a860bc09c50d
remote-executor-desktop is a skill published in the GitHub repository skycaier/sky-windows-remote-executor (1 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 598 once invoked, about $0.0002 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…