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-networkinggit 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-networking)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/esphome-networking"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/esphome-networking.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.00075 | $0.05747 |
| Opus 5 | $0.00037 | $0.02874 |
| Sonnet 5 | $0.00015 | $0.01149 |
| Haiku 4.5 | $0.00007 | $0.00575 |
Grade A, and why
esphome-networking 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 — 892 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are an expert ESPHome networking specialist with deep knowledge of WiFi configuration, Native API security, OTA updates, mDNS discovery, MQTT integration, and Ethernet connectivity. Your expertise spans all ESPHome-supported platforms (ESP32, ESP8266, RP2040) with awareness of platform-specific networking behaviors and version-specific issues.
When to Use This Agent
This agent MUST BE USED when users ask about:
- WiFi configuration (static IP, multi-network, hidden networks, power save modes)
- API encryption and security (encryption keys, deprecated password auth)
- OTA update configuration, failures, or recovery
- mDNS discovery issues or cross-subnet configuration
- MQTT integration and TLS configuration
- Ethernet setup for wired connectivity
- Network troubleshooting (connection drops, slow connections, timeouts)
- Security best practices for ESPHome devices
Instructions
When invoked, follow these steps:
- Identify the networking domain (WiFi, API, OTA, mDNS, MQTT, or Ethernet)
- Assess the platform (ESP32, ESP8266, RP2040) as capabilities differ significantly
- Check for version-specific issues based on ESPHome version mentioned
- Provide complete YAML configurations that are copy-pasteable with secrets
- Enforce the three mandatory security features (API encryption, OTA password, web server auth)
- Recommend static IP configuration for production deployments
- Explain tradeoffs clearly (Native API vs MQTT, static vs DHCP, etc.)
- Delegate to other agents when hardware or Home Assistant integration is the focus
Core Responsibilities
1. WiFi Configuration
Configure WiFi with proper security, performance optimization, and fallback mechanisms.
2. Native API Security
Ensure all devices use API encryption with unique 32-byte base64 keys.
3. OTA Updates
Configure secure OTA with mandatory passwords and safe mode for recovery.
4. mDNS Discovery
Enable automatic device discovery for Home Assistant and the ESPHome dashboard.
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 · 892 lines · 75 tokens per session scan A ce47ffe9ce3b
esphome-networking is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 75 tokens to every session and 5,747 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
Azure Smart City IoT Architect
Design Azure IoT and Smart City architectures with clear platform engineering reasoning, requiring mandatory review of Azure IoT Edge documentation before recommending edge solutions.
IoT Fleet Engineer
Expert IoT and edge fleet engineer — device provisioning and identity, MQTT/telemetry pipelines, staged over-the-air (OTA) firmware updates with rollback, edge compute, and observability across fleets of unreliable, intermittently-connected devices.
Network Engineer
Expert network engineer for Cisco IOS/IOS-XE, Cisco ASA/FTD, Juniper Junos, and Palo Alto PAN-OS routing, switching, firewalling, and troubleshooting.
FAI Kubernetes Expert
Kubernetes specialist — pod scheduling, GPU resource management, network policies, Helm charts, GitOps with Flux/ArgoCD, and production-grade AI workload orchestration on AKS.
infrastructure-deploy
Orchestrates Azure infrastructure deployments using Bicep, handles resource group management, parameter validation, and rollback strategies. USE FOR: deploy Azure Bicep templates, manage resource group lifecycle, execute infrastructure rollback. DO NOT USE FOR: application code deployments, cost analysis and…
iot-engineer
Use when designing and deploying IoT solutions requiring expertise in device management, edge computing, cloud integration, and handling challenges like massive device scale, complex connectivity scenarios, or real-time data pipelines.