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-display-authorgit 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-display-author)<a href="https://agentmods.dev/skills/nolte/claude-home-assistant/ha-esphome-display-author"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-esphome-display-author/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-display-author"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-esphome-display-author.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.00265 | $0.02938 |
| Opus 5.5 | $0.00106 | $0.01175 |
| Sonnet 5.5 | $0.00053 | $0.00588 |
| Haiku 4.5 | $0.00026 | $0.00294 |
Grade A, and why
ha-esphome-display-author 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA ESPHome Display Author
Spec: spec/claude/ha-esphome-display-author/en.md (EN canonical) / spec/claude/ha-esphome-display-author/de.md (DE translation). Grounding specs: spec/ha/esp32-s3-box-display/en.md (rendering mechanics, canonical for the 320×240 panel), spec/ha/esp32-s3-box-display-design/en.md (the design system layered on those mechanics — palette, type scale, icon scale, structure), and spec/ha/esp32-s3-box/en.md §Display binding (the hardware side, referenced not repeated).
Authors what is on the screen and where — the pages, the redraw discipline, the geometry, and the design system applied to them — for one display of one device per invocation.
Why this is a skill, not an agent
- Mid-flow approval is the contract (decisive): the rendering-path choice is expensive to reverse (page lambdas and widget trees share no code, so switching later is a rewrite of the whole UI), and the state-to-page mapping is a design conversation, not a derivation.
- Iterated visual work in the current context: layouts are adjusted in rounds — a zone moved, a font size dropped, a string truncated — which is main-thread territory.
- Counter-dimension considered: the asset and memory budgeting is mechanical enough to isolate (agent bias), but it feeds directly back into the layout decisions being discussed; skill wins.
When this skill activates
The user wants content on an ESPHome device's panel — "was soll auf dem Display der Box stehen", "add a page for the timer", "design the idle screen" — for a device whose display is already bound.
When NOT to activate
- the panel's hardware binding (SPI pins,
model:preset,invert_colors, backlight light) →ha-esphome-config-augment, taking the values fromspec/ha/esp32-s3-box/en.md - where the displayed values come from →
ha-esphome-binding-add - the voice-assistant lifecycle that drives the reference screens →
ha-esphome-voice-satellite-add - a Divoom Pixoo 64 →
ha-pixoo-solution(a different device family with its own specs) - a panel geometry other than 320×240 → the grounding specs' constants are specific to this panel: the zone grid to 320×240, and the design spec's legibility table and icon sizes to its 2.4-inch, 166.7 ppi geometry. State that limit rather than extrapolating
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 · 109 lines · 265 tokens per session scan A 6e5a5120175f
ha-esphome-display-author is a skill published in the GitHub repository nolte/claude-home-assistant (1 stars, last pushed 1mo ago), licensed MIT. It adds 265 tokens to every session and 2,938 once invoked, about $0.0011 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…