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.
npx skills add gtapps/claude-code-hermit --skill ha-house-statusgit clone --depth 1 https://github.com/gtapps/claude-code-hermitWrote 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/skills/gtapps/claude-code-hermit/ha-house-status)<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/ha-house-status"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/ha-house-status/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/skills/gtapps/claude-code-hermit/ha-house-status"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/ha-house-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00334 |
| Opus 5.5 | $0.00015 | $0.00134 |
| Sonnet 5.5 | $0.00007 | $0.00067 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
ha-house-status 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 1mo 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.
This is a copy
89% identical to ha-house-status — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
HA House Status
Steps
- Call
GetDateTimefor current time and date. - Call
GetLiveContextfor the live house snapshot. - Use the stored language from OPERATOR.md (
## HA hermitsection) for all output. - Check
.claude-code-hermit/raw/snapshot-ha-normalized-latest.jsonmodification time. If older than 24 hours or missing, append a warning to the status output:"Context snapshot is stale — run
/claude-code-homeassistant-hermit:ha-refresh-contextfor accurate entity data." - Present a human-readable summary in the stored locale, organized by:
- Presence: who is home / away
- Lights: which are on
- Covers/Blinds: positions
- Climate: temperatures, HVAC state
- Media: what's playing
- Security: alarm state (read-only, never actuate)
- Notable: anything unusual (devices unavailable, unexpected states)
Format
Keep the summary concise. Use bullet points. Group by area if the house has distinct areas. Highlight anything that looks unusual or worth investigating.
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.
- 1mo ago First seen · 32 lines · 37 tokens per session scan A c1b52cc7d5b0
ha-house-status is a skill published in the GitHub repository gtapps/claude-code-hermit (82 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 334 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to ha-house-status, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
volt-firmware
Produce a complete firmware architecture spec for a described device — layer diagram, module responsibilities, HAL interface definitions, key state machines, RTOS decision. Use when asked to "design firmware architecture", "plan embedded firmware", "architect an IoT device", "how should I structure this firmware", or…
volt-ota
Produce a complete OTA update system design — partition layout, update flow, rollback conditions, validation checks, fleet management approach, failure modes and recovery. Use when asked about "OTA updates", "firmware updates over the air", "how do I update devices in the field", "OTA strategy", or "remote firmware…
volt-power
Power management audit — analyze sleep modes, wake sources, power state machines, radio duty cycles, and battery life estimates. Use when asked to "audit power usage", "optimize battery life", "review power management", "why is my battery draining", "power budget analysis", or "sleep mode review".
volt-driver
Build a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I/O and clean HAL abstraction. Use when asked to "write a driver", "I2C device", "BLE service", "MQTT client", or "sensor integration".
volt-recon
Firmware reconnaissance for takeover — inventory the MCU, peripherals, RTOS, protocols, OTA, power management, and assess code quality with risk flags. Use when asked to "understand this firmware", "device inventory", or "embedded assessment".
ha-house-status
Get a quick live status of the house via MCP. Shows lights, covers, climate, presence, and notable states. Use when the operator asks about house state.