Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gtapps/claude-code-hermit/plugin install claude-code-homeassistant-hermitWrote 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/gtapps/claude-code-hermit/ha-snapshot-restore)<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/ha-snapshot-restore"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/ha-snapshot-restore/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/gtapps/claude-code-hermit/ha-snapshot-restore"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/ha-snapshot-restore.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.00069 | $0.00600 |
| Opus 5.5 | $0.00028 | $0.00240 |
| Sonnet 5.5 | $0.00014 | $0.00120 |
| Haiku 4.5 | $0.00007 | $0.00060 |
Grade A, and why
ha-snapshot-restore 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 1mo 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.
This is a copy
92% identical to ha-snapshot-restore — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA Snapshot / Restore
Purpose
Make changes reversible: capture an entity set's current state before testing a new automation or applying a risky change, then restore those exact states if it misbehaves. Capture is read-only; restore actuates devices in one scene.apply call.
Capture (read-only)
${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha snapshot-states --name <label> [--domains light,cover,climate,switch] [--entities <id> ...]
--namelabels the snapshot (defaultsnapshot); it becomes part of the artifact filename.--domainsselects which domains to capture (comma-separated; defaultlight,cover,climate,switch).--entitiescaptures an explicit list instead of whole domains.- Writes
.claude-code-hermit/raw/snapshot-ha-states-<label>-latest.json(plus a timestamped copy). Only restore-relevant attributes are stored.
Restore (actuation — gated)
${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha restore-states <artifact>
Restore is the plugin's one direct device-actuation path, so it runs through the same ha_safety_mode policy as every other actuation:
- strict (explicit): if the snapshot contains any sensitive entity (lock, alarm, security-keyworded cover/switch), restore is blocked and exits non-zero with
blocked:trueand a suggestion to surface it as a proposal. Non-sensitive entities (lights, climate) restore normally. - ask: show the affected entities before restoration; Claude Code requests native approval for sensitive targets before the command executes.
- A successful restore writes an audit report under
.claude-code-hermit/raw/audit-ha-restore-*.
Output contract
Capture prints { ok, name, captured, entities, report_path, message }.
Restore prints { ok, blocked, applied, entities, sensitive, reason, ... }. Exit code is 0 only when ok is true.
Failure modes
- HA unreachable → CLI exits non-zero with an error message.
- A snapshot with no matching entities → capture reports
captured: 0; restore reports an error. - Restore replays state + captured attributes via
scene.apply; for cover position and climate setpoints the result depends on what HA's scene integration can reproduce — verify the outcome rather than assuming an exact match.
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.
- 1mo ago Changed 75af3a395c21
- 1mo ago First seen · 49 lines · 69 tokens per session scan A 9563936fee6a
ha-snapshot-restore is a skill published in the GitHub repository gtapps/claude-code-hermit (82 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 600 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to ha-snapshot-restore, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
volt-firmware
Produce a complete firmware architecture spec for a described device — layer diagram, module responsibilities, HAL interface definitions, key state machines, RTOS decision. Use when asked to "design firmware architecture", "plan embedded firmware", "architect an IoT device", "how should I structure this firmware", or…
volt-ota
Produce a complete OTA update system design — partition layout, update flow, rollback conditions, validation checks, fleet management approach, failure modes and recovery. Use when asked about "OTA updates", "firmware updates over the air", "how do I update devices in the field", "OTA strategy", or "remote firmware…
volt-power
Power management audit — analyze sleep modes, wake sources, power state machines, radio duty cycles, and battery life estimates. Use when asked to "audit power usage", "optimize battery life", "review power management", "why is my battery draining", "power budget analysis", or "sleep mode review".
volt-driver
Build a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I/O and clean HAL abstraction. Use when asked to "write a driver", "I2C device", "BLE service", "MQTT client", or "sensor integration".
volt-recon
Firmware reconnaissance for takeover — inventory the MCU, peripherals, RTOS, protocols, OTA, power management, and assess code quality with risk flags. Use when asked to "understand this firmware", "device inventory", or "embedded assessment".
ha-house-status
Get a quick live status of the house via MCP. Shows lights, covers, climate, presence, and notable states. Use when the operator asks about house state.