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-update-check)<a href="https://agentmods.dev/skills/gtapps/hermitd/ha-update-check"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/ha-update-check/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-update-check"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/ha-update-check.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.00059 | $0.00724 |
| Opus 5.5 | $0.00024 | $0.00290 |
| Sonnet 5.5 | $0.00012 | $0.00145 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
ha-update-check 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-update-check — 91% identical, 6 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 Update Check
Purpose
Home Assistant surfaces pending updates as update.* entities — one domain covering Core, OS/Supervisor, add-ons, and HACS integrations, each carrying installed_version/latest_version/release_summary/release_url. This skill lists what's pending and reports it in a fixed format the proposal pipeline can fan out into per-update proposals.
Native fields only — no web fetch for breaking-change detail (keeps this check cheap; fetch on accept if that's ever needed). HA-native skipped_version is honored: an update the operator skipped in the HA UI stays quiet here too.
Steps
Run the update check via the CLI:
${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha updates
The CLI:
- Fetches live entity states and filters to
update.*entities wherestate == "on"(an update is pending) and the pending version hasn't been skipped in HA. - Classifies each into a tier:
core(HA Core),os(Operating System),supervisor,addon, orhacs. Core/OS/Supervisor are recognized by their well-known entity_ids; add-ons are recognized by the native backup capability they advertise (HA'ssupported_featuresBACKUP bit), which HACS/custom-integration updates lack; anything without it aggregates into thehacsbucket rather than risking noise. - Prints the findings block to stdout in the documented format below.
Output contract
reflect --check-id ha-update-check --check hermitd-homeassistant:ha-update-check routes the findings block through the proposal pipeline. The stdout shape is fixed:
ha-update-check findings — <date>
Updates pending: N
- [core] Home Assistant Core: 2026.6.3 → 2026.7.1 — <release_url>
- [addon] Mosquitto broker: 6.4 → 6.5 — <release_url>
- [hacs] 7 HACS updates pending
If nothing is pending: No actionable findings. (no updates pending).
If HA is unreachable: No actionable findings. (skipped: <error>).
Keep stdout to this shape — no prose, no extra sections. Each proposal title should carry the concrete target version (e.g. [ha-update] HA Core → 2026.7.1) — that keeps same-version re-emits byte-identical so proposal-triage reliably suppresses repeats; Core/OS/Supervisor and each add-on become individual proposals, all pending HACS updates aggregate into one.
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 · 59 tokens per session scan A fb4816b8a8dc
ha-update-check is a skill published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 724 once invoked, about $0.0002 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
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-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-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".
kicad-jlcpcb-workflow
Use this skill when the user asks to "design a PCB", "make a board", "build a PCB project", "order from JLCPCB", "create a schematic", "source LCSC parts", "wire up a board", "generate a PCB from a BOM", or any KiCad + JLCPCB workflow. Also use when working with .kicadpro or .kicadpcb files. Handles project setup…