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 komal-SkyNET/claude-skill-homeassistant --skill home-assistant-managergit clone --depth 1 https://github.com/komal-SkyNET/claude-skill-homeassistantWrote 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/komal-skynet/claude-skill-homeassistant/home-assistant-manager)<a href="https://agentmods.dev/skills/komal-skynet/claude-skill-homeassistant/home-assistant-manager"><img src="https://agentmods.dev/badge/skills/komal-skynet/claude-skill-homeassistant/home-assistant-manager/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/komal-skynet/claude-skill-homeassistant/home-assistant-manager"><img src="https://agentmods.dev/badge/skills/komal-skynet/claude-skill-homeassistant/home-assistant-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 18 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00092 | $0.01796 |
| Opus 5 | $0.00046 | $0.00898 |
| Sonnet 5 | $0.00018 | $0.00359 |
| Haiku 4.5 | $0.00009 | $0.00180 |
Grade A, and why
home-assistant-manager 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Home Assistant Manager
Operate a remote Home Assistant instance precisely: make a change, get it live, prove it worked. Optimize for the fewest safe round-trips.
Assumptions
- The repo you're editing is the HA
/configdir, git-connected to the instance. Edits aren't live until pulled on the instance. [email protected]in examples is a placeholder. Resolve the real user/host once (project CLAUDE.md,~/.ssh/config, or ask) and if it isn't recorded in the project CLAUDE.md yet, add it so future sessions skip this step.- Access via one or more of:
hass-cli(REST), SSHha, or an MCP server (see below). - Only edit
.yaml/.yml/.md. Never read/write.envorsecrets.yaml; use!secret.
Remote access — pick the right tool
- SSH
ha— always works, needs no local env. Use forha core check|restart|logs|info. hass-cli(REST) — state/service calls, but needsHASS_SERVER/HASS_TOKENin the shell before the session starts. If they're unset, hass-cli falls back to the wrong host (localhost) and errors — don't retry, check[ -n "$HASS_TOKEN" ]once, then use SSH or MCP instead.- MCP (preferred when available) — first-class tools for live state/control, no env
juggling. Official
mcp_serverintegration (HA core ≥2025.2) or communityha-mcp(richer, 80+ tools). Use it instead of shelling out when present.
The deploy pipeline (the one canonical flow)
Changes are not live until step 4.
- Edit YAML locally.
- Validate:
ssh [email protected] "ha core check"(slow, ~30-60s — see "when to skip" below). - Commit + push:
git add … && git commit -m "…" && git push. - Make it live:
ssh [email protected] "cd /config && git pull". - Apply: reload if possible, else restart (table below).
- Verify (next section).
Rapid iteration: skip git and scp straight to the instance, then reload — good for
dashboards and tight test loops. Commit to git only once stable.
scp automations.yaml [email protected]:/config/ → reload.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 128 lines · 92 tokens per session scan A 9c571d72391a
home-assistant-manager is a skill published in the GitHub repository komal-SkyNET/claude-skill-homeassistant (957 stars, last pushed 2mo ago), licensed MIT. It adds 92 tokens to every session and 1,796 once invoked, about $0.0005 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 skills, from other repositories
arena-bridge
Skill and protocol specification for AI agents (Arena.ai Agent Mode, Claude Code, Codex, Cursor, and custom agentic frameworks) interacting with Skainet Bridge.
Home Assistant Automation
Automate smart home devices and create intelligent home automation workflows with Home Assistant.
ha-integration-solution
Plans and orchestrates a complete Home Assistant Python custom-integration backend from a result-oriented device/cloud/API requirement, driven by a chosen quality-scale target tier (Bronze–Platinum), so the user never picks individual skills. Decomposes the requirement into a minimal dependency-ordered plan for the…
ha-esphome-solution
Plans and orchestrates a complete ESPHome device or fleet result from a requirement, so the user never has to pick which ESPHome skill produces what. Decomposes it into the minimal dependency-ordered set of artifacts across the ha-esphome- family — repository layout and packages, the device file, sensors and buses…
ha-integration-scaffold
Scaffolds a complete Home Assistant Custom Integration skeleton — manifest, lifecycle, config flow, coordinator, entity, platforms, translations, icons, diagnostics, plus pytest harness — in one go, conformant to every MUST pattern in spec/ha/. Activate on phrasings like "scaffold a new HA Custom Integration", "create…
ha-automation-solution
Plans and orchestrates a complete Home Assistant YAML solution from a result-oriented requirement, so the user never has to pick which authoring skill to use. Decomposes the requirement into the minimal combination of artifacts across the ha-automation skill family, presents a dependency-ordered artifact plan for…