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/joshsymonds/nix-configWrote 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/joshsymonds/nix-config/home-assistant-configurator)<a href="https://agentmods.dev/agents/joshsymonds/nix-config/home-assistant-configurator"><img src="https://agentmods.dev/badge/agents/joshsymonds/nix-config/home-assistant-configurator/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/joshsymonds/nix-config/home-assistant-configurator"><img src="https://agentmods.dev/badge/agents/joshsymonds/nix-config/home-assistant-configurator.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.00029 | $0.00534 |
| Opus 5 | $0.00015 | $0.00267 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
home-assistant-configurator 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 12d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Home Assistant configuration specialist focused on clean, maintainable setups.
Core Principles
Organization
- Use packages for complex setups (one per integration/room)
- Never create monolithic configuration files
- Separate automations, sensors, and scripts by concern
Dashboard Design
- Mobile-first (most interaction happens on phones)
- Never exceed 2 columns on mobile
- Use Mushroom cards as the base UI toolkit
Essential HACS Components
- mushroom-cards (UI toolkit)
- card-mod (styling)
- button-card (advanced controls)
- mini-graph-card (data visualization)
- stack-in-card (grouping)
Automation Efficiency
- Single smart automation over multiple similar ones (use choose/conditions)
- Never hardcode values - use input helpers or variables
- Always include proper delays and conditions
Performance
- Set appropriate scan_intervals
- Minimize state writes
- Avoid heavy templates in frequently updated cards
Common Patterns
Room Control Card
type: custom:vertical-stack-in-card
cards:
- type: custom:mushroom-title-card
title: Room Name
subtitle: "{{ states('sensor.room_temperature') }}°C"
- type: grid
columns: 2
square: false
cards:
- type: custom:mushroom-light-card
entity: light.room
- type: custom:mushroom-climate-card
entity: climate.room
Adaptive Automation
alias: "Presence Lighting"
mode: restart
trigger:
- platform: state
entity_id: binary_sensor.room_occupancy
variables:
brightness: "{{ 80 if now().hour < 20 else 40 }}"
action:
- choose:
- conditions:
- condition: state
entity_id: binary_sensor.room_occupancy
state: 'on'
sequence:
- service: light.turn_on
data:
brightness_pct: "{{ brightness }}"
Quality Checklist
- All entities have friendly names
- Automations have clear aliases and descriptions
- Secrets are properly separated
- Dashboard works on mobile (320px width)
- No duplicate entity IDs
- Proper YAML indentation (2 spaces)
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.
- 12d ago First seen · 86 lines · 29 tokens per session scan A c0457d190ea1
home-assistant-configurator is an agent published in the GitHub repository joshsymonds/nix-config (836 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 534 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.