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-apply-update)<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/ha-apply-update"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/ha-apply-update/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-apply-update"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/ha-apply-update.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.00058 | $0.00692 |
| Opus 5.5 | $0.00023 | $0.00277 |
| Sonnet 5.5 | $0.00012 | $0.00138 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
ha-apply-update 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
88% identical to ha-apply-update — 6 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply HA Update
When this runs
Invoked from proposal-act's Accept flow for a [ha-update] proposal (originated by /claude-code-homeassistant-hermit:ha-update-check). The proposal body carries the entity_id, tier (core/os/supervisor/addon/hacs), and target version.
Steps
-
Read the flag: check
ha_update_auto_applyin.claude-code-hermit/config.json.- Absent or
false: this is advisory-only. Resolve the proposal — tell the operator the update is available and where (Settings → System → Updatesin the HA UI), and stop. Do not callupdate.install. true: show the entity and target version, then continue.
- Absent or
-
Branch on tier (from the proposal body). The
addonvshacssplit is defined by the native backup capability:ha-update-checktiers an entityaddonprecisely when it advertises HA's BACKUP update feature, sobackup:trueis always valid for anaddonproposal, and ahacsentity is one that can't back itself up (hence the separate full-backup step).addon:${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha call-service update.install --data '{"entity_id":"<entity_id>","backup":true}'. HA backs up the add-on natively and rolls back on install failure. Report the result to the operator once done.hacs(an individual HACS entity accepted out of an aggregated proposal; HACS entities don't support the nativebackupparameter): first${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha create-backup --agent-ids <configured agent>. If the backup call is blocked or fails, stop and stay advisory; tell the operator why. Only on a successful backup:ha call-service update.install --data '{"entity_id":"<entity_id>"}'.core/os/supervisor: never auto-apply, even with the flag on. Show the tier, installed/available versions, and dashboard-access impact. Run:ha call-service update.install --data '{"entity_id":"<entity_id>","backup":true}'.
-
Report: read the command's JSON output (
ok/message). On success, tell the operator the update installed and that an audit is at.claude-code-hermit/raw/audit-ha-call-service-*. On failure, surface the error verbatim and leave the proposal open rather than resolving it.
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 20c286b88afd
- 1mo ago First seen · 31 lines · 58 tokens per session scan A 65f5a88ed4a2
ha-apply-update is a skill published in the GitHub repository gtapps/claude-code-hermit (82 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 692 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to ha-apply-update, differing in 6 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.