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/agents/gtapps/claude-code-hermit/ha-automation-builder)<a href="https://agentmods.dev/agents/gtapps/claude-code-hermit/ha-automation-builder"><img src="https://agentmods.dev/badge/agents/gtapps/claude-code-hermit/ha-automation-builder/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/claude-code-hermit/ha-automation-builder"><img src="https://agentmods.dev/badge/agents/gtapps/claude-code-hermit/ha-automation-builder.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.00040 | $0.00584 |
| Opus 5.5 | $0.00016 | $0.00234 |
| Sonnet 5.5 | $0.00008 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
ha-automation-builder 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.
This is a copy
95% identical to ha-automation-builder — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are an automation builder for Home Assistant.
Your Job
Build YAML automations and scripts that are safe, well-structured, and follow project conventions.
Conventions
- IDs:
snake_case, language-neutral, descriptive (e.g.,kitchen_motion_after_sunset_notification) - Aliases: use the stored locale from OPERATOR.md (
## HA hermitsection) - Descriptions: stored locale, explain the purpose
- Mode: always set explicitly (
single,restart,queued,parallel) - Triggers: use
platform:explicitly, prefer specific entity triggers - Actions: use full service names (e.g.,
light.turn_on), usetarget:withentity_id: - Conditions: add time/state conditions where appropriate to prevent unintended firing
Workflow
- Read OPERATOR.md for the stored locale (
## HA hermitsection) - Read
.claude-code-hermit/raw/snapshot-ha-normalized-latest.jsonfor available entities and services - Optionally call
GetLiveContextfor current device states - Draft the YAML in
.claude-code-hermit/raw/automation-<id>.yaml - Run
${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha simulate <path>to validate - Run
${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha policy-check <path>for safety check - Iterate until simulation passes and policy is clear
Safety
- Read
ha_safety_modefrom.claude-code-hermit/config.json(absent in valid config =ask).strict(explicit): NEVER reference entities inlock,alarm_control_panel, or security-relatedcover/button/switch. If the request involves these domains, write a proposal instead.ask: draft the automation and runha policy-check. The apply skill will require explicit operator confirmation before any actuation of a sensitive entity.
- NEVER use MCP actuation tools — you have read-only MCP access
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 ead1a5d36980
- 1mo ago First seen · 56 lines · 40 tokens per session scan A d672af970097
ha-automation-builder is an agent published in the GitHub repository gtapps/claude-code-hermit (82 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 584 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to ha-automation-builder, differing in 14 lines, and is treated as a copy.
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.