Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gtapps/claude-code-hermit/plugin install claude-code-homeassistant-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-presence-report)<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/ha-presence-report"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/ha-presence-report/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-presence-report"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/ha-presence-report.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.00063 | $0.01026 |
| Opus 5.5 | $0.00025 | $0.00410 |
| Sonnet 5.5 | $0.00013 | $0.00205 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
ha-presence-report 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-presence-report — 15 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA Presence Report
Steps
-
Call
GetDateTimefor the current time reference. Read the stored locale from.claude-code-hermit/OPERATOR.mdunder## HA hermit(fall back to English if absent). -
Read
.claude-code-hermit/raw/snapshot-ha-normalized-latest.json.- If the file is missing or older than 24 hours, prepend a staleness warning to the output:
"Context snapshot is stale — run
/claude-code-homeassistant-hermit:ha-refresh-contextfor accurate data." - Filter
entity_indexto keys starting withperson.ordevice_tracker.. If no matching keys exist, emit "no presence entities found — presence tracking isn't configured in this HA instance" and stop. Do not proceed to the history fetch. - From the matched entities derive:
- Current state: value of
statefield (home / away / unknown / unavailable) andlast_changed→ "since HH:MM" relative to now. - Reliability flags: mark an entity unreliable if
state == "unavailable"ORlast_changedis more than 48 hours ago (stale tracker).
- Current state: value of
- If the file is missing or older than 24 hours, prepend a staleness warning to the output:
-
Run:
${CLAUDE_PLUGIN_ROOT}/bin/ha-agent-lab ha fetch-history \ --window-days 7 \ --entities "device_tracker.*" "person.*" \ --include-transitionsThis writes
.claude-code-hermit/raw/snapshot-ha-history-7d-latest.json. -
Read
snapshot-ha-history-7d-latest.json. For each presence entity:- Recent transitions: show the last 5 entries from
transitions(ordered chronologically), formatted asHH:MM DD-Mon — <state>. - Home/away split: derive from
state_durations— what percentage of the window was "home" vs "away". - Typical activity windows: bucket the
transitionslist by UTC hour, keyed on direction: transitions tohomeare arrivals, transitions toawayare departures. Report the top 1–2 arrival hours and departure hours separately (e.g. "typically arrives around 18:00 UTC, leaves around 08:00 UTC"). With ≥7d of data and ≥5 total transitions, state the windows; below that threshold, say "insufficient data for pattern detection." (hour_histogramcounts all events regardless of direction, so use it only as a fallback for entities whose states aren't home/away.)
- Recent transitions: show the last 5 entries from
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 Changed · -4 lines 8872cfdcc87e
- 1mo ago First seen · 76 lines · 63 tokens per session scan A 75cc00a08a0c
ha-presence-report is a skill published in the GitHub repository gtapps/claude-code-hermit (82 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 1,026 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to ha-presence-report, differing in 15 lines, and is treated as a copy.
Other skills, from other repositories
windows-ops
Comprehensive Windows workstation operations - diagnose slow boot, failing drives, BSOD crashes, startup bloat, runaway processes, event logs. Use for: Windows is slow, slow bootup, won't boot, blue screen, BSOD, kernel crash, drive failing, SMART errors, disk errors, Event 41, Event 129, storahci reset, BugCheck…
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…
vigil-instrument
Instrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks. Outputs actual code and config, not a plan. Use when asked to "add monitoring", "instrument this", "add logging", "set up tracing", or "observability".
apex-review
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
touch-audit
Mobile audit — app size, startup time, crash reporting, store compliance, accessibility, offline behavior. Use when asked for "mobile review", "app store readiness", "mobile performance", or "crash analysis".