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.
/plugin marketplace add narrowstacks/claude-homeassistant-pluginsnpx agentmods add plugins/narrowstacks/claude-homeassistant-plugins/esphome-configgit clone --depth 1 https://github.com/narrowstacks/claude-homeassistant-pluginsWrote 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/plugins/narrowstacks/claude-homeassistant-plugins/esphome-config)<a href="https://agentmods.dev/plugins/narrowstacks/claude-homeassistant-plugins/esphome-config"><img src="https://agentmods.dev/badge/plugins/narrowstacks/claude-homeassistant-plugins/esphome-config.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
esphome-config 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 4d 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.
What it actually says
{
"name": "esphome-config",
"description": "Skill to create and modify ESPHome device configuration files.",
"version": "1.0.0",
"author": {
"name": "narrowstacks"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 56 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 4d ago First seen · 9 lines scan A 31b9f44f6fdc
esphome-config is a plugin published in the GitHub repository narrowstacks/claude-homeassistant-plugins (3 stars, last pushed 10mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
kicad-pro
KiCad MCP Pro plugin for schematic review, PCB design assistance, DRC/ERC validation, DFM checks, and manufacturing release workflows.
world2agent
Give Claude Code real-time awareness of external events via World2Agent sensors (Hacker News, GitHub, stocks, X, calendars, and more).
visionclaude
VisionClaude — Let Claude see the world through your eyes. Camera + voice + Meta Ray-Ban glasses bridge for Claude Code via iOS app.
analog-design-em
Electromagnetic solving for passives/antennas, S-parameter extraction and lumped-model fitting.
atopile-dev
Design electronics with atopile's declarative DSL (ato). Provides language reference, package creation guides, and electronics design workflows for AI agents working with .ato files and PCB design.
analog-design-architecture
Signal-chain budgeting, per-block spec allocation, and feasibility for analog/mixed-signal.