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-ci-scaffoldgit 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-ci-scaffold)<a href="https://agentmods.dev/skills/nolte/claude-home-assistant/ha-esphome-ci-scaffold"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-esphome-ci-scaffold/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-ci-scaffold"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-esphome-ci-scaffold.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.00220 | $0.01970 |
| Opus 5.5 | $0.00088 | $0.00788 |
| Sonnet 5.5 | $0.00044 | $0.00394 |
| Haiku 4.5 | $0.00022 | $0.00197 |
Grade A, and why
ha-esphome-ci-scaffold 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA ESPHome CI Scaffold
Spec: spec/claude/ha-esphome-ci-scaffold/en.md (EN canonical) / spec/claude/ha-esphome-ci-scaffold/de.md (DE translation). Grounding spec: spec/ha/esphome-project-structure/en.md §Validation. Workflow mechanics follow the inherited spec/project/github-actions-best-practices/ and spec/project/continuous-integration/.
Scaffolds the validation pipeline of an ESPHome fleet — the one gate that catches the failure mode a shared-package repository is built to produce.
Why this is a skill, not an agent
- Mid-flow approval is the contract (decisive): the credential strategy for a validation run, the compile cadence, and the ESPHome version floor are operator decisions with cost and security consequences.
- Quick, targeted change in the current context: one or two workflow files in the repository the conversation is scoped to.
- Counter-dimension considered: enumerating the fleet and the existing pipeline is self-contained (agent bias), but the resulting workflow is iterated with the operator; the read-only audit of an existing pipeline is a different job and belongs to
cicd-pipeline-reviewer(nolte-shared) /ha-esphome-fleet-reviewer.
When this skill activates
The user wants an ESPHome repository validated automatically — "ESPHome-Configs in CI prüfen", "add a GitHub Actions workflow for my device configs", "how do I catch a broken package before it reaches a device".
When NOT to activate
- the repository tree and the package architecture →
ha-esphome-fleet-scaffold - a red run to triage →
workflow-health-triage(from the nolte-shared plugin; when it is not installed, triage the run againstspec/project/workflow-health/directly) - an audit of the existing pipeline →
cicd-pipeline-reviewer(nolte-shared, general) /ha-esphome-fleet-reviewer(ESPHome-specific, always available here) - CI for a Python custom integration →
ha-integration-ci-scaffold - local compile, flash, or OTA rollout → the ESPHome toolchain / operator
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 · 96 lines · 220 tokens per session scan A cf47ddbae327
ha-esphome-ci-scaffold is a skill published in the GitHub repository nolte/claude-home-assistant (1 stars, last pushed 1mo ago), licensed MIT. It adds 220 tokens to every session and 1,970 once invoked, about $0.0009 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…
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
agent-mobile-release-manager
Specialist subagent: App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta…
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…