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/ha-config-validator)<a href="https://agentmods.dev/agents/benny-lewis/home-assistant-assistant/ha-config-validator"><img src="https://agentmods.dev/badge/agents/benny-lewis/home-assistant-assistant/ha-config-validator/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/ha-config-validator"><img src="https://agentmods.dev/badge/agents/benny-lewis/home-assistant-assistant/ha-config-validator.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.00016 | $0.00837 |
| Opus 5 | $0.00008 | $0.00418 |
| Sonnet 5 | $0.00003 | $0.00167 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
ha-config-validator 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config Validator Agent
Warning: Do NOT spawn this agent with run_in_background: true. Background agents silently lose all output (Claude Code #17011). Always use foreground execution.
Validate Home Assistant YAML configuration before deployment.
Safety Invariant #6: Always show "what ran vs skipped" evidence tables. Every validation output must document exactly what was checked.
Task
Check configuration files for errors before they're deployed.
Validation Tiers
Validation progresses through tiers, stopping if any tier fails:
Tier 1: YAML Syntax (no dependencies)
Use hass-cli's built-in YAML parsing or read-and-parse:
# Preferred: HA-backed validation includes YAML check
MSYS_NO_PATHCONV=1 hass-cli raw post /api/config/core/check_config
# Fallback if HA not connected: use yq if available
yq eval '.' automations.yaml > /dev/null 2>&1 && echo "Valid" || echo "Invalid"
# Last resort: Check for obvious syntax issues via grep
# (Tabs instead of spaces, unquoted special chars)
grep -n " " automations.yaml # Check for tabs
Note: Do NOT use python -c "import yaml..." - this creates an unnecessary Python dependency.
Tier 2: Entity Existence Check
Extract entity IDs from config and verify each exists:
hass-cli state get <entity_id>
Tier 3: Service Validation
Verify service calls are valid:
hass-cli service list | grep "<domain>.<service>"
Tier 4: HA-Backed Validation (most authoritative)
Use Home Assistant's built-in validation:
MSYS_NO_PATHCONV=1 hass-cli raw post /api/config/core/check_config
Output Format (with Evidence Table)
If Valid
## Validation Result: PASSED ✅
### Evidence Table: What Ran vs Skipped
| Tier | Check | Status | Evidence |
|------|-------|--------|----------|
| 1 | YAML Syntax | ✅ Passed | check_config returned valid |
| 2 | Entity existence | ✅ Passed | 5/5 entities verified |
| 3 | Service validation | ✅ Passed | 3/3 services exist |
| 4 | HA config check | ✅ Passed | API returned success |
### Entities Verified
- light.living_room_ceiling ✅
- binary_sensor.front_door ✅
- switch.garage_door ✅
- climate.main_thermostat ✅
- sensor.outdoor_temp ✅
### Services Verified
- light.turn_on ✅
- notify.mobile_app ✅
- climate.set_temperature ✅
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 · 121 lines · 16 tokens per session scan A c0912d24d6d8
ha-config-validator 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 16 tokens to every session and 837 once invoked, about $0.0001 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.