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 sandover/agent-skills --skill windows-vm-controlgit clone --depth 1 https://github.com/sandover/agent-skillsWrote 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/sandover/agent-skills/windows-vm-control)<a href="https://agentmods.dev/skills/sandover/agent-skills/windows-vm-control"><img src="https://agentmods.dev/badge/skills/sandover/agent-skills/windows-vm-control.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.00058 | $0.01201 |
| Opus 5 | $0.00029 | $0.00600 |
| Sonnet 5 | $0.00012 | $0.00240 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
windows-vm-control 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 6d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
18 files 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.
- agents/openai.yaml 247 B
- references/access-recovery.md 4.9 KB
- references/command-work.md 4.1 KB
- references/desktop-work.md 3.8 KB
- references/lifecycle.md 2.6 KB
- references/managed-delegation.md 7.9 KB
- scripts/guest-probe.ps1 2.7 KB runs code
- scripts/interactive-runner.ps1 2.7 KB runs code
- scripts/restore-openssh.ps1 5.6 KB runs code
- scripts/windows-codex-run 12 KB
- scripts/windows-codex-session 29 KB
- scripts/windows-vm-interactive-run 7.1 KB
- scripts/windows-vm-powershell 6.6 KB
- scripts/windows-vm-recover-ssh 9.3 KB
- scripts/windows-vm-status 9.4 KB
- scripts/windows-vmrun 6.5 KB
- tests/host-regressions.zsh 22 KB runs code
- tests/test_windows_codex_session.py 17 KB runs code
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.
- 6d ago First seen · 83 lines · 58 tokens per session scan A 706114803d05
windows-vm-control is a skill published in the GitHub repository sandover/agent-skills (4 stars, last pushed 26d ago), with no licence file. It adds 58 tokens to every session and 1,201 once invoked, about $0.0003 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 skills, from other repositories
yao-geo-tracking
Build a company-specific GEO backend tracking plan from a company name plus optional supporting information, using authoritative retrieval anchored on the official website, business-feature recognition, and market-aware GEO monitoring methods, then deliver a direct-vs-indirect attribution design, data model, roadmap…
yao-geo-comparison-builder
A tool for creating evidence-based Chinese brand comparison content for AI search and answer platforms. It compares a target brand with competitors, traditional approaches, or self-built solutions.
yao-geo-explainer-builder
A tool for creating detailed, evidence-based educational articles about a topic for Chinese AI search and answer platforms. It can include explanations, how-to steps, selection guidance, common mistakes, FAQs, and a glossary.
yao-geo-page-audit
Diagnose a website page or small page set for GEO readiness with authoritative public evidence, systematic page analysis, code/content/schema fixes, and four-format Chinese report delivery.
yao-geo-brand-graph
A method for building a brand entity knowledge graph from company information, websites, products, customers, people, places, evidence sources, and use cases. A knowledge graph records entities and the supported relationships between them.
yao-deepseek-crawler
Use when a user provides DeepSeek web AI-search keywords, repeat count, target entity, and entity type, then needs repeated fresh-window crawls aggregated into JSON plus a Kami HTML GEO report. Not for generic website crawling, DeepSeek API chat, SEO writing, or one-off answer generation.