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 ESJavadex/claude-homeassistant-pluginsnpx agentmods add plugins/esjavadex/claude-homeassistant-plugins/homeassistant-configgit clone --depth 1 https://github.com/ESJavadex/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/esjavadex/claude-homeassistant-plugins/homeassistant-config)<a href="https://agentmods.dev/plugins/esjavadex/claude-homeassistant-plugins/homeassistant-config"><img src="https://agentmods.dev/badge/plugins/esjavadex/claude-homeassistant-plugins/homeassistant-config.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
homeassistant-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 6d 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": "homeassistant-config",
"description": "Create, modify, and troubleshoot Home Assistant configuration files and Lovelace dashboards",
"version": "1.5.2",
"author": {
"name": "claude-homeassistant-plugins"
},
"agents": ["./agents/ha-suggestions.md"],
"hooks": {
"PreToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/hooks/validate-before-save.sh"
}
]
}
]
}
}
What it installs
The manifest is a name and a version. 1 skill, 1 command, 1 agent travel with it, and installing the plugin installs all of them — 129 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.
- 6d ago First seen · 23 lines scan A ee81589950cf
homeassistant-config is a plugin published in the GitHub repository ESJavadex/claude-homeassistant-plugins (26 stars, last pushed 9mo 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-30.
Other plugins, from other repositories
tokenbudget
Enforces a daily token budget for Claude Code. Works with any backend — Bedrock, Vertex, direct API, or subscription.
migrate-tool
Generate database migrations and code migration scripts for framework upgrades.
load-tester
Load and stress testing for APIs and web services.
fuse-react
Expert React 19 with hooks, TanStack Router, Zustand, React Hook Form, Testing Library, shadcn/ui, and SOLID principles.
fuse-rules
Global rules for all Claude Code sessions: APEX workflow, SOLID/DRY enforcement, project detection, agent delegation, frontend/git standards.
r2g-skills
RTL-to-GDS-to-Graph skill collection. eda-install detects the machine and installs + verifies the open-source EDA toolchain (with a no-sudo conda path). signoff-loop drives an open-source EDA flow (Yosys + OpenROAD-flow-scripts + KLayout + Magic + Netgen + OpenRCX) from a spec or RTL to signed-off GDSII (DRC, LVS…