hv-snapshot

hv-snapshot is a skill for Claude Code, Codex from bryanjbelanger/desktop-hypervisor-mcp. It costs 48 tokens per session (449 once invoked), scanned A, original, MIT.

A guide for taking, listing, restoring, and cleaning up snapshots of VirtualBox or VMware virtual machines. A snapshot records a VM's state so it can be returned to that point later.

In plain words
What is it for?
Protecting a VM before upgrades or configuration changes, rolling it back, and managing old snapshot chains.
Why use it?
It provides a rollback point before risky changes and explains that restoring removes disk changes made afterward.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Protecting a VM before upgrades or configuration changes, rolling it back, and managing old snapshot chains.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bryanjbelanger/desktop-hypervisor-mcp/hv-snapshot
Install

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.

Any agent
npx skills add bryanjbelanger/desktop-hypervisor-mcp --skill hv-snapshot
Clone the repo
git clone --depth 1 https://github.com/bryanjbelanger/desktop-hypervisor-mcp

Made for: Claude Code, Codex.

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.

agentmods badge for hv-snapshot

README.md
[![agentmods](https://agentmods.dev/badge/skills/bryanjbelanger/desktop-hypervisor-mcp/hv-snapshot/github.svg)](https://agentmods.dev/skills/bryanjbelanger/desktop-hypervisor-mcp/hv-snapshot)
Your own site
<a href="https://agentmods.dev/skills/bryanjbelanger/desktop-hypervisor-mcp/hv-snapshot"><img src="https://agentmods.dev/badge/skills/bryanjbelanger/desktop-hypervisor-mcp/hv-snapshot/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.

agentmods 80×15 button for hv-snapshot

Your own site · 80×15
<a href="https://agentmods.dev/skills/bryanjbelanger/desktop-hypervisor-mcp/hv-snapshot"><img src="https://agentmods.dev/badge/skills/bryanjbelanger/desktop-hypervisor-mcp/hv-snapshot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 449 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.00449
Opus 5 $0.00024 $0.00225
Sonnet 5 $0.00010 $0.00090
Haiku 4.5 $0.00005 $0.00045

Measured 9d ago against content hash 8def365c2261, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

hv-snapshot 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 9d 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.

skills/hv-snapshot/SKILL.md · 45 lines

What it actually says

Snapshot workflows

Preflight

Requires the desktop-hypervisor MCP server: confirm mcp__hypervisor__snapshot is available. Missing → stop; register with claude mcp add --scope user hypervisor -- <binary> (MCP Registry: io.github.bryanjbelanger/desktop-hypervisor-mcp) and restart the session.

Pre-change safety snapshot (default habit)

Before any risky in-VM operation the user describes (upgrades, config surgery): snapshot action=take vm=NAME name=pre-<change>-<YYYYMMDD> Running VMs snapshot fine (state is captured); note a running snapshot includes memory and is larger.

Rollback

  1. snapshot action=list vm=NAME tree=true — confirm the target exists; show the user the hierarchy.
  2. A restore DISCARDS current disk state. Stop the VM first (vm_lifecycle action=stop vm=NAME, hard=true if the guest hangs).
  3. snapshot action=restore vm=NAME name=SNAP (on VirtualBox an empty name restores the most recent). Start the VM again afterward.
  4. Never restore without naming what will be lost (time window since snapshot).

Hygiene

  • Snapshots are deltas; long chains slow I/O and bloat disk. When a change is confirmed good, delete its safety snapshot: snapshot action=delete vm=NAME name=SNAP (children=true cascades — VMware only; VirtualBox deletes merge into the chain one at a time).
  • Audit: vm_info action=list, then snapshot action=list tree=true per VM; flag chains deeper than 3 or older than 30 days.

Report

Snapshot name taken or restored, chain depth after the operation, and anything flagged for cleanup.

Changes

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.

  1. 9d ago First seen · 45 lines · 48 tokens per session scan A 8def365c2261

Subscribe to this mod's changes

hv-snapshot is a skill published in the GitHub repository bryanjbelanger/desktop-hypervisor-mcp (0 stars, last pushed 24d ago), licensed MIT. It adds 48 tokens to every session and 449 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

gke-ai-troubleshooting-jobset-interruption

Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…

google/skills · 83 tokens

gke-workload-troubleshooting

Diagnoses GKE workload failures (CrashLoopBackOff, OOMKilled, ImagePullBackOff, Pending, etc.) via logs and events. Use when pods fail to start or crash repeatedly. Don't use for GKE cluster infrastructure provisioning, node pool creation, or non-Kubernetes Google Cloud services.

google/skills · 69 tokens

gke-node-notready

Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…

google/skills · 112 tokens

gke-ai-troubleshooting-handle-disruption-gpu-tpu

Diagnoses, predicts, and mitigates node disruptions during Compute Engine host maintenance and hardware or software maintenance events for GPU and TPU workloads on GKE. Use when diagnosing node disruptions, predicting host maintenance events on GPU/TPU nodepools, inspecting node interruption PromQL metrics, auditing…

google/skills · 117 tokens

agentcore-investigation

Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.

awslabs/mcp · 52 tokens

troubleshoot-sandbox

Troubleshoot OpenSandbox issues by running diagnostics (logs, inspect, events, summary) via CLI or HTTP API to diagnose sandbox failures like OOM, crash, image pull errors, network problems, etc.

opensandbox-group/OpenSandbox · 48 tokens