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/hermitd/plugin install hermitd-homeassistantWrote 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/hermitd/ha-snapshot-restore)<a href="https://agentmods.dev/skills/gtapps/hermitd/ha-snapshot-restore"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/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/hermitd/ha-snapshot-restore"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/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.00594 |
| Opus 5.5 | $0.00028 | $0.00238 |
| Sonnet 5.5 | $0.00014 | $0.00119 |
| Haiku 4.5 | $0.00007 | $0.00059 |
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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ha-snapshot-restore — 92% identical, 4 lines differ
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
.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
.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.
- 11d ago First seen · 49 lines · 69 tokens per session scan A f6bba683d2c2
ha-snapshot-restore is a skill published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 594 once invoked, about $0.0003 per session on Opus 5.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-10-02.
Other skills, from other repositories
ros2-robotics
Best practices for ROS 2 robotics development, covering package structure, nodes, topics/services/actions, launch files, QoS, tf2 transforms, and testing. Use when creating ROS 2 packages, writing nodes in rclpy or rclcpp, defining custom messages/services/actions, writing launch files, configuring QoS profiles…
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…
proof-e2e
Build E2E test specs for critical user journeys — Playwright or Cypress, page objects, setup/teardown, CI config. Use when asked to "write E2E tests", "end-to-end testing", "browser tests", "UI tests", or "Playwright tests".
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…
proof-strategy
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".
mean-tester
Mean test another agent when someone asks you to test, check or break it. Invoke on "test @agent", "mean test @agent", "check whether @agent works", on "continue " or "rerun " in a new message, or on "continue" in a thread where you already reported a campaign, and on "Judge this recorded exchange".