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.
npx skills add nolte/claude-home-assistant --skill ha-esphome-solutiongit clone --depth 1 https://github.com/nolte/claude-home-assistantWrote 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/nolte/claude-home-assistant/ha-esphome-solution)<a href="https://agentmods.dev/skills/nolte/claude-home-assistant/ha-esphome-solution"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-esphome-solution/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/nolte/claude-home-assistant/ha-esphome-solution"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-esphome-solution.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.00205 | $0.03327 |
| Opus 5.5 | $0.00082 | $0.01331 |
| Sonnet 5.5 | $0.00041 | $0.00665 |
| Haiku 4.5 | $0.00020 | $0.00333 |
Grade A, and why
ha-esphome-solution 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA ESPHome Solution
Spec: spec/claude/ha-esphome-solution/en.md (EN canonical) / spec/claude/ha-esphome-solution/de.md (DE translation). This spec governs the front-door dispatch/plan contract, structurally consistent with its ha-{integration,lovelace,automation,pixoo}-solution siblings; the grounding specs below govern the ESPHome artifacts themselves.
Grounding specs: spec/ha/esphome-config-patterns/en.md, spec/ha/esphome-project-structure/en.md, spec/ha/esphome-ha-driven-content/en.md, and — where the device is one — spec/ha/esp32-s3-box/en.md, spec/ha/esp32-s3-box-display/en.md, spec/ha/esp32-s3-box-display-design/en.md, spec/ha/assist-pipeline/en.md.
This skill is the front door to the ESPHome skill family. It generates nothing itself: it decomposes the requirement, plans the combination, and dispatches the owning skills, each of which owns its generation and spec conformance.
Why this is a skill, not an agent
- Plan-before-generate gate — the artifact plan must be presented and explicitly approved before any generation; that human-visible gate is core to the contract and an agent's fire-and-forget shape would lose it.
- Mid-flow interactivity — the clarifying questions (which board, which values come from Home Assistant, is there a screen, is it a voice satellite) and the plan confirmation are per-run dialogues.
- Orchestrator that dispatches other skills — the skill-orchestrates-skill default keeps the entry point in skill form, exactly as the sibling
*-solutionskills do. - Counter-dimension considered: the per-artifact generation could run as parallel agents, but the identity threading (device name → package parameters → entity ids → redraw script) must stay visible in the operator's context; skill wins.
When this skill activates
The user describes an ESPHome result that likely needs more than one artifact and should not have to know which skill produces what — "ein Node im Gewächshaus, der Feuchte misst und den Sollwert aus HA anzeigt", "set up my ESPHome repo and add the first two plugs", "make the box a voice satellite with a status screen".
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 First seen · 153 lines · 205 tokens per session scan A 63b8fd48a919
ha-esphome-solution is a skill published in the GitHub repository nolte/claude-home-assistant (1 stars, last pushed 1mo ago), licensed MIT. It adds 205 tokens to every session and 3,327 once invoked, about $0.0008 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-08-31.
Other skills, from other repositories
esphome
Use when flashing or automating ESP32/ESP8266 firmware with ESPHome 2026.10 — YAML configuration with esphome/esp32/api/ota/wifi blocks, esphome run/compile/logs/upload CLI, OTA updates, native API encryption, substitutions and packages; also for 'Component not found', OTA upload failures, boot loops after flashing…
technical-troubleshooting
Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
aurora
Aurora Smart Home orchestrator — routing layer for all smart home skills. Use this skill when the user asks ANY smart home question and you need to decide which skill to invoke, or when a task spans multiple skills (e.g., "build a sensor that shows on a dashboard and triggers automations"). Invoke aurora FIRST before…
ESPHome
ESPHome device configuration, firmware, and IoT product development. Covers ESP32, ESP32-S3, ESP32-C3, ESP32-C6, ESP32-H2, ESP32-P4, ESP8266, RP2040, RP2350, nRF52, LibreTiny, Shelly, Sonoff, Tuya, BLE proxy, Matter firmware, Thread, Zigbee, GPIO, sensor YAML, LVGL displays, LED strips, voice assistant hardware…
HA Integration Dev
Home Assistant custom integration development in Python. Covers customcomponents, DataUpdateCoordinator, configflow, OAuth2, conversation agent, HACS publishing, device registry, entity platforms, services, repair issues, diagnostics, Bluetooth integrations, and multi-coordinator patterns.
Node-RED
Node-RED visual automation flows for Home Assistant. Covers visual automation, flow JSON, trigger-state, api-call-service, function nodes, context storage, timer patterns, error handling, and node-red-contrib-home-assistant-websocket nodes. Use when user mentions "Node-RED", "flow", "visual automation", or…