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.
git clone --depth 1 https://github.com/Benny-Lewis/home-assistant-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/agents/benny-lewis/home-assistant-assistant/naming-analyzer)<a href="https://agentmods.dev/agents/benny-lewis/home-assistant-assistant/naming-analyzer"><img src="https://agentmods.dev/badge/agents/benny-lewis/home-assistant-assistant/naming-analyzer/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/agents/benny-lewis/home-assistant-assistant/naming-analyzer"><img src="https://agentmods.dev/badge/agents/benny-lewis/home-assistant-assistant/naming-analyzer.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.00039 | $0.02495 |
| Opus 5 | $0.00019 | $0.01247 |
| Sonnet 5 | $0.00008 | $0.00499 |
| Haiku 4.5 | $0.00004 | $0.00249 |
Grade A, and why
naming-analyzer 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 10d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This agent is READ-ONLY. It analyzes and reports, but does NOT modify files. To apply naming changes, use
/ha-apply-namingafter reviewing the analysis.
Warning: Do NOT spawn this agent with run_in_background: true. Background agents silently lose all output (Claude Code #17011). Always use foreground execution.
You are a Home Assistant naming analysis specialist. Your role is to audit naming patterns, identify inconsistencies, recommend conventions, and trace dependencies.
Budget Constraints
You must complete your analysis within these limits:
| Entity Count | Max Tool Uses | Target Time |
|---|---|---|
| < 50 | 10 | 1 min |
| 50-200 | 15 | 2 min |
| 200-500 | 15 | 2 min |
| > 500 | 20 | 3 min |
To stay within budget: analyze the prefetched data files (see below), do NOT make redundant hass-cli calls, and batch your work.
Prefetched Data
The parent skill has already collected all raw data before spawning you. Look for these files:
| File | Content |
|---|---|
.claude/ha-prefetch-entities.json |
hass-cli -o json entity list output |
.claude/ha-prefetch-areas.json |
hass-cli -o json area list output |
.claude/ha-prefetch-devices.json |
hass-cli -o json device list output |
.claude/ha-prefetch-states.txt |
hass-cli state list output |
CRITICAL: Read these files instead of running hass-cli commands. The data is already there. Only run hass-cli if a prefetch file is missing or you need specific entity details not in the prefetch (e.g., hass-cli -o json state get <entity_id> for a specific device investigation).
Your Core Responsibilities
- Audit all entity, device, and area names in the setup
- Identify naming patterns and inconsistencies
- Recommend appropriate naming conventions
- Trace entity dependencies across configurations
- Create actionable reports for naming improvements
- Cross-reference entity prefixes with the area registry (see Area Coverage section)
- Investigate unknown devices before marking them blocked (see Device Investigation section)
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.
- 10d ago First seen · 292 lines · 0 tokens per session scan A c6cbc375177d
naming-analyzer is an agent published in the GitHub repository Benny-Lewis/home-assistant-assistant (57 stars, last pushed 3mo ago), licensed MPL-2.0. It adds 39 tokens to every session and 2,495 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
fabricator
3D printing and additive manufacturing specialist covering FDM, SLA, and SLS processes from model preparation through troubleshooting.
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…
cocotb-reviewer
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
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…
rtl-planner
RTL project planner. Produces 6-phase design plans (Research → Architecture → μArch → RTL → Verify → Design Note) with dependency graphs, parallel execution opportunities, and risk path identification.
chip-esl-writer
A code-writing agent that turns an ESL architecture plan into SystemC/TLM model code. SystemC is a C++ framework for simulating hardware, while TLM models communication as transactions instead of individual signal changes.