What is ha-analyze-patterns?

A Home Assistant analysis routine that examines device history and current entity patterns. Home Assistant is software for monitoring and controlling smart-home devices.

Use it to review recent activity, find inactive automations, identify optimization opportunities, and investigate energy anomalies.

It helps reveal automations that no longer run, unused devices, and unusual energy behaviour that may otherwise go unnoticed.

ha-analyze-patterns — Skill for Claude Code by gtapps

Install

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.

Claude Code

/plugin marketplace add gtapps/claude-code-hermit

Claude Code

/plugin install claude-code-homeassistant-hermit

Made for: Claude Code.

Or install claude-code-homeassistant-hermit, the plugin that ships this one along with the rest of its 18 skills, 3 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/ha-analyze-patterns.svg)](https://agentmods.dev/skills/gtapps/claude-code-hermit/ha-analyze-patterns)

Your own site

<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="Measured on agentmods" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,464 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01464
Opus 5	$0.00017	$0.00732
Sonnet 5	$0.00007	$0.00293
Haiku 4.5	$0.00003	$0.00146

Measured 3d ago against content hash 955307aeee26, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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 3d 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.

plugins/claude-code-homeassistant-hermit/skills/ha-analyze-patterns/SKILL.md · 80 lines

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.json if it exists.
Get live context: Call GetLiveContext and GetDateTime via MCP for current state.
Fetch history: Run ${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha fetch-history --window-days 7. On non-zero exit, log a single line to SHELL.md ## Monitoring (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 both entity_index and silence_summary (added by every context refresh). Also read .claude-code-hermit/raw/snapshot-ha-history-7d-latest.json if 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: true entries 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.
From silence_summary.suppressed_entity_domains:
- Note in Markdown artifact that these domains are already covered by ha-integration-health.

Read the full file on GitHub · 80 lines

Changes

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.

3d ago First seen · 80 lines · 35 tokens per session scan A 955307aeee26

Subscribe to this mod's changes

ha-analyze-patterns is a skill published in the GitHub repository gtapps/claude-code-hermit (74 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,464 once invoked, about $0.0002 per session on Opus 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.

Analytics and metrics Claude Code Hardware and IoT ai ai-agent anthropic claude claude-code-plugin

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. Phase 1.6 handles project…

BeckhamLabsLLC/kicad-jlcpcb · 145 tokens

especialista-em-engenharia-de-hardware

Especialista em Engenharia de Hardware. Use para design eletrônico, microcontroladores, PCB, firmware embarcado, sinais, energia e prototipagem. Palavras-chave: hardware, eletrônica, microcontrolador, PCB, embarcado, firmware, Arduino.

euwebertdefreitas/ai-skills-for-claude-code · 63 tokens

qector-hardware-engineer

Physical-layer quantum circuits, detector-error-model preparation, qLDPC reasoning, and honest target-device hardware reporting for QECTOR. The bundled library MCP server is app-free; the companion bench server adds DEM inspection, DEM collapse, code-family introspection, and hardware probes (all Provisional).…

GuillaumeLessard/qector-claude-plugin · 103 tokens

ha-analyze-patterns