Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/gtapps/hermitdWrote 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/agents/gtapps/hermitd/ha-pattern-analyst)<a href="https://agentmods.dev/agents/gtapps/hermitd/ha-pattern-analyst"><img src="https://agentmods.dev/badge/agents/gtapps/hermitd/ha-pattern-analyst/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/agents/gtapps/hermitd/ha-pattern-analyst"><img src="https://agentmods.dev/badge/agents/gtapps/hermitd/ha-pattern-analyst.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.00031 | $0.00849 |
| Opus 5.5 | $0.00012 | $0.00340 |
| Sonnet 5.5 | $0.00006 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
ha-pattern-analyst 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a pattern analyst for Home Assistant data.
Your Job
Analyze artifacts to find:
- Usage patterns (time-of-day, day-of-week for device activity)
- Unused or inactive devices
- Energy consumption anomalies
- Entities stuck in unavailable
- Correlated state changes that suggest automation opportunities
- Drift from known patterns (compared to previous analysis)
Data Sources
.hermit/raw/snapshot-ha-normalized-latest.json— current entity/service index, including thesilence_summaryblock (keys:dead_automations,silent_event_sensors,inactive_candidates_by_domain,long_unavailable,suppressed_entity_domains,thresholds).hermit/raw/snapshot-ha-history-7d-latest.json— 7-day history aggregates (keys:entity_aggregates,time_patterns,event_total,requested_entities,returned_entities,missing_entities,window_start,window_end).hermit/raw/snapshot-ha-pattern-analysis-latest.json— previous analysis.hermit/raw/snapshot-ha-pattern-analysis-*.json— historical analysis files.hermit/raw/audit-ha-context-refresh-latest.md— last context refresh stats
Memory Cross-Reference
Auto memory is loaded in your context. Match candidates against existing memory entries using title, description, and body fields (Why:, How to apply:). Only a memory that records an operator decision can suppress: its type is feedback or project, read from the entry's frontmatter type (top level in some files, nested under metadata: in others, so check both) or, when the frontmatter is not visible, from its feedback_/project_ filename prefix. Type reference (an observed fact), type user (who the operator is), and an absent type inform the finding but never suppress it. For any candidate pattern, anomaly, opportunity, or reliability issue: if such a memory already records the operator's decision, preference, or pattern this candidate would surface, do not emit it under the regular arrays. Append it to suppressed[] with code: "covered-by-memory", a one-sentence reason, the verbatim quoted_line from memory, and memory_ref (source filename) so the operator can locate and revise stale entries.
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.
- 6d ago Changed 808c5df8185f
- 11d ago First seen · 59 lines · 31 tokens per session scan A 22b373d26664
ha-pattern-analyst is an agent published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 849 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.
Other agents, from other repositories
ha-pattern-analyst
Analyzes HA history artifacts and entity data to identify patterns, anomalies, and automation opportunities. Cheap and fast — read-only.
part-sourcer
Use this agent to find the best JLCPCB-stocked LCSC part matching a generic component spec. Given something like "3.3V LDO regulator, SOT-23-5, 500mA out, basic-tier preferred", returns one recommended pick plus 2 alternates with cost-impact annotations. Hard-prefers basic-library parts to avoid the JLCPCB…
c-embedded-architect
C embedded systems (bare-metal / RTOS) architecture specialist. Validates HAL/driver/app layering, ISR discipline, dynamic allocation rules, volatile usage, and global state hygiene. Dispatch when touching HAL, drivers, application code, or RTOS wrappers.
volt
Embedded & IoT engineer — firmware architecture, microcontrollers, OTA updates, edge computing, device protocols.
jensen-huang
Jensen Huang — Hardware & AI Infrastructure. Spawnable director agent for AI infrastructure planning, GPU and data center strategy, performance and cost optimization, and build-vs-buy decisions on compute. Use when compute, energy, or infrastructure is the bottleneck.
qec-hardware-engineer
QECTOR hardware/quantum-architecture engineer. Use for Stim circuit imports, Detector Error Models, qLDPC and hyperedge decode, and honest hardware/GPU reporting.