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-analyze-patterns)<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/ha-analyze-patterns"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/ha-analyze-patterns/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-analyze-patterns"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/ha-analyze-patterns.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.00035 | $0.01535 |
| Opus 5.5 | $0.00014 | $0.00614 |
| Sonnet 5.5 | $0.00007 | $0.00307 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
ha-analyze-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA Pattern Analysis
Steps
-
Load existing analysis: Read
.claude-code-hermit/raw/snapshot-ha-pattern-analysis-latest.jsonif it exists. -
Get live context: Call
GetLiveContextandGetDateTimevia MCP for current state. -
Fetch history: Run
${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha fetch-history --window-days 7. On non-zero exit, pipe one line into.claude-code-hermit/bin/hermit-run task note .claude-code-hermit <id>only inside an open record's turn (otherwise skip the note) (history fetch failed: <stderr first line>) and continue: the skill proceeds using Phase 1 silence findings only. Do not surface the fetch failure to scheduled-check stdout. -
Read normalized inventory: Read
.claude-code-hermit/raw/snapshot-ha-normalized-latest.json. Extract bothentity_indexandsilence_summary(added by every context refresh). Also read.claude-code-hermit/raw/snapshot-ha-history-7d-latest.jsonif present. -
Analyze patterns from silence_summary and history:
From
silence_summary.dead_automations(enabled automations not fired in 30+ days):- Each entry is an actionable Reliability issue:
"automation.X has not fired in N days (enabled)". never_fired: trueentries get special phrasing:"automation.X has never fired (enabled but never triggered)".
From
silence_summary.silent_event_sensors(motion/door/window sensors silent for 7+ days):- Each entry is an actionable Reliability issue:
"binary_sensor.X (<device_class>) — no events in N days".
From
silence_summary.long_unavailable(individual entities unavailable 7+ days, domain not already degraded):- Each entry is a Reliability issue:
"entity.X unavailable for N days".
From
silence_summary.inactive_candidates_by_domain(lights/switches/covers/climates unchanged for 7+ days):- Surface in the Markdown patterns artifact only. Do not include in the stdout findings block — these are informational, not actionable without corroboration.
- Each entry is an actionable Reliability issue:
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 042a6ebbd825
- 1mo ago Changed bb25dc48380e
- 1mo ago First seen · 80 lines · 35 tokens per session scan A 955307aeee26
ha-analyze-patterns is a skill published in the GitHub repository gtapps/claude-code-hermit (82 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,535 once invoked, about $0.0001 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-09-03.
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.