agentmods.dev

ha-analyze-patterns

ha-analyze-patterns is a skill for Claude Code from gtapps/hermitd. It costs 35 tokens per session (1,527 once invoked), scanned A, original, MIT.

A Home Assistant history and device-pattern analysis routine. Home Assistant is software that monitors and controls smart-home devices, and this routine examines their activity over time.

In plain words
What is it for?
It helps find automation opportunities, identify inactive or never-used devices, and detect energy anomalies from recent history.
Why use it?
It helps reveal automations that rarely run, unused devices, and unusual energy behaviour that may be missed in a live status view.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the hermitd-homeassistant plugin — 18 skills, 3 agents shipped together

not rated 79repo +5 changed 6d ago A scan 35 tokens original MIT

Good fit It helps find automation opportunities, identify inactive or never-used devices, and detect energy anomalies from recent history.

Compare 6 skills from other repositories ↓
View source ↗ gtapps/hermitd hermitd.dev
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/hermitd
Claude Code
/plugin install hermitd-homeassistant

Made for: Claude Code.

Or install hermitd-homeassistant, 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.

agentmods badge for ha-analyze-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/gtapps/hermitd/ha-analyze-patterns/github.svg)](https://agentmods.dev/skills/gtapps/hermitd/ha-analyze-patterns)
Your own site
<a href="https://agentmods.dev/skills/gtapps/hermitd/ha-analyze-patterns"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/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.

agentmods 80×15 button for ha-analyze-patterns

Your own site · 80×15
<a href="https://agentmods.dev/skills/gtapps/hermitd/ha-analyze-patterns"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/ha-analyze-patterns.svg" alt="Reviewed on agentmods" width="80" 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,527 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.01527
Opus 5.5 $0.00014 $0.00611
Sonnet 5.5 $0.00007 $0.00305
Haiku 4.5 $0.00003 $0.00153

Measured 6d ago against content hash d23abc8c7979, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-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 6d 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/hermitd-homeassistant/skills/ha-analyze-patterns/SKILL.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

HA Pattern Analysis

Steps

  1. Load existing analysis: Read .hermit/raw/snapshot-ha-pattern-analysis-latest.json if it exists.

  2. Get live context: Call GetLiveContext and GetDateTime via MCP for current state.

  3. Fetch history: Run ${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha fetch-history --window-days 7. On non-zero exit, pipe one line into .hermit/bin/hermitd-run task note .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.

  4. Read normalized inventory: Read .hermit/raw/snapshot-ha-normalized-latest.json. Extract both entity_index and silence_summary (added by every context refresh). Also read .hermit/raw/snapshot-ha-history-7d-latest.json if present.

  5. 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 · 82 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.

  1. 6d ago Changed · +2 lines d23abc8c7979
  2. 11d ago First seen · 80 lines · 35 tokens per session scan A 767dc817697f

Subscribe to this mod's changes

ha-analyze-patterns is a skill published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,527 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-10-02.

Analytics and metricsClaude CodeHardware and IoTaiai-agentanthropicclaudeclaude-code-plugin
Related

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…

tonone-ai/tonone · 70 tokens

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…

tonone-ai/tonone · 76 tokens

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

tonone-ai/tonone · 65 tokens

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

tonone-ai/tonone · 63 tokens

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

tonone-ai/tonone · 52 tokens

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…

BeckhamLabsLLC/kicad-jlcpcb · 140 tokens