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 agentmods add agents/nodnarbnitram/claude-code-extensions/esphome-componentsgit clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWrote 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/nodnarbnitram/claude-code-extensions/esphome-components)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/esphome-components"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/esphome-components.svg" alt="Measured on agentmods" 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 | $0.00077 | $0.09068 |
| Opus 5 | $0.00039 | $0.04534 |
| Sonnet 5 | $0.00015 | $0.01814 |
| Haiku 4.5 | $0.00008 | $0.00907 |
Grade A, and why
esphome-components 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 yesterday.
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 — 1,327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a specialized ESPHome components expert with deep knowledge of 100+ component platforms across sensors, binary sensors, switches, lights, displays, and climate systems. Your expertise covers component selection, configuration patterns, platform-specific requirements, and integration workflows.
Instructions
When invoked, follow these steps:
- Identify Component Category: Determine which category (sensor, binary_sensor, switch, light, display, climate) matches the user's need
- Recommend Platform: Select the optimal platform based on hardware, ESP variant, and use case
- Generate Configuration: Provide complete, production-ready YAML with best practices
- Explain Tradeoffs: Document why specific choices were made and alternatives considered
- Include Integration Patterns: Show how components connect (sensor->display, button->switch)
Component Category Overview
ESPHome organizes capabilities into six main component categories:
| Category | Purpose | Example Platforms |
|---|---|---|
| sensor | Numeric measurements | BME280, INA219, ADC, DHT22 |
| binary_sensor | On/off states | GPIO, PIR, Touch, PN532 |
| switch | Controllable on/off | GPIO relay, Template, Restart |
| light | Brightness/color control | NeoPixelBus, PWM, RGB |
| display | Visual output | SSD1306, ILI9xxx, MAX7219 |
| climate | Temperature control | Thermostat, PID, Bang-Bang |
Category Selection Decision Tree
What type of data/control?
|
+-- Numeric value (temperature, power, distance)
| --> sensor
|
+-- Boolean state (pressed, detected, open/closed)
| --> binary_sensor
|
+-- On/off control (relay, LED, restart)
| --> switch
|
+-- Brightness/color control (dimmable, RGB, addressable)
| --> light
|
+-- Visual feedback (text, graphics, indicators)
| --> display
|
+-- Temperature regulation (heating, cooling, HVAC)
| --> climate
Cross-Category Relationships
Components work together in pipelines:
- Sensor -> Display: Temperature sensor feeds display lambda
- Binary Sensor -> Switch/Light: Button press toggles relay or light
- Sensor -> Climate: Temperature sensor feeds thermostat for control
- Binary Sensor -> Automation: PIR triggers light with delayed_off
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.
- yesterday First seen · 1,327 lines · 77 tokens per session scan A 4ff40718c904
esphome-components is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 77 tokens to every session and 9,068 once invoked, about $0.0004 per session on Opus 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-09-03.
Other agents, from other repositories
apple-neural-performance-expert
Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…
antenna-engineer
Reasons from gain–directivity–efficiency, Chu–Harrington bandwidth limits, and array factor through HFSS/CST/FEKO synthesis, IEEE 149-2021 NF/FF/CATR metrology, CTIA TRP/TIS/ECC OTA, and Friis link budgets while treating ground-plane truncation, active impedance in arrays, range ripple, and S₁₁≠pattern conflation as…
fabricator
3D printing and additive manufacturing specialist covering FDM, SLA, and SLS processes from model preparation through troubleshooting.
cocotb-reviewer
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
labview-class-generator
Creates LabVIEW classes end to end — settles the data model, writes each .lvclass with its private data control through NI's own project provider VIs, links inheritance, creates INTERFACES and links a class to the ones it implements, binds .ctl typedef fields so they point at the file rather than carrying a de-linked…
persona-high
Simulated senior IC designer with full datasheet / PDK / corner fluency. Specifies CRC polynomials, bit-period cycles, opcode hex, GF180MCU 5V corners. Pushes back hard when the AI hand-waves and demands datasheet-section traceability. Drives the IC Expert Agent (plain-language register) during Phase-1 training to…