ha-mcp is an unofficial Model Context Protocol server that lets AI assistants interact with Home Assistant, including controlling devices, checking states, running services, and managing automations. Home Assistant users can connect it through the HA-MCP custom component or another supported setup. The catalogue entries are skills, agents, instructions, settings, and an MCP configuration for working with it.
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 homeassistant-ai/ha-mcp --skill contributors-updategit clone --depth 1 https://github.com/homeassistant-ai/ha-mcpWrote 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/homeassistant-ai/ha-mcp/contributors-update)<a href="https://agentmods.dev/skills/homeassistant-ai/ha-mcp/contributors-update"><img src="https://agentmods.dev/badge/skills/homeassistant-ai/ha-mcp/contributors-update/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/homeassistant-ai/ha-mcp/contributors-update"><img src="https://agentmods.dev/badge/skills/homeassistant-ai/ha-mcp/contributors-update.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.00017 | $0.00909 |
| Opus 5 | $0.00009 | $0.00454 |
| Sonnet 5 | $0.00003 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
contributors-update 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 11d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributors Update
Workflow
1. Ensure a clean, up-to-date master
Locate the primary checkout even when the skill is invoked from a worktree, then update and inspect master:
PRIMARY_CHECKOUT="$(git worktree list --porcelain | grep -m1 '^worktree ' | cut -d' ' -f2-)"
git -C "$PRIMARY_CHECKOUT" checkout master
git -C "$PRIMARY_CHECKOUT" pull --ff-only origin master
git -C "$PRIMARY_CHECKOUT" status --short
cd "$PRIMARY_CHECKOUT"
Stop if the primary checkout is dirty. Do not stash, overwrite, or mix the contributor update with other changes. This workflow qualifies for the documentation-only exception in AGENTS.md, allowing the approved README.md change to be committed directly to master without a PR.
2. Find the cutoff date
Look for the most recent commit with the marker [contributors-updated] in the merged origin/master history. Do not search --all: marker commits on abandoned branches must not affect the cutoff.
git log origin/master --oneline --grep="\[contributors-updated\]" -5
If a marker commit is found:
- Get its date:
git show <hash> --format="%ci" -s - Cutoff = that date minus 1 week (as overlap margin)
If no marker commit is found:
- Cutoff = today minus 2 months
3. List merged PRs since the cutoff date
Push the merge-date constraint into GitHub's search so filtering happens before the result limit:
gh pr list --repo homeassistant-ai/ha-mcp --state merged \
--search "merged:>=YYYY-MM-DD" --limit 1000 \
--json number,title,author,mergedAt \
--jq '.[] | "\(.number) \(.author.login) \(.title)"'
Replace YYYY-MM-DD with the computed cutoff date.
4. Identify new contributors
Read the current README.md ### Contributors and ### Maintainers sections to get all existing handles.
Filter PR authors, excluding:
- Bot accounts (
github-actions,dependabot,gemini-code-assist,copilot, etc.) - Existing maintainers and contributors already in the README
- The repo owner (
julienld)
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.
- 11d ago First seen · 102 lines · 17 tokens per session scan A f1ab3962de03
contributors-update is a skill published in the GitHub repository homeassistant-ai/ha-mcp (4,682 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 909 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 skills, from other repositories
aurora
Aurora Smart Home orchestrator — routing layer for all smart home skills. Use this skill when the user asks ANY smart home question and you need to decide which skill to invoke, or when a task spans multiple skills (e.g., "build a sensor that shows on a dashboard and triggers automations"). Invoke aurora FIRST before…
ESPHome
ESPHome device configuration, firmware, and IoT product development. Covers ESP32, ESP32-S3, ESP32-C3, ESP32-C6, ESP32-H2, ESP32-P4, ESP8266, RP2040, RP2350, nRF52, LibreTiny, Shelly, Sonoff, Tuya, BLE proxy, Matter firmware, Thread, Zigbee, GPIO, sensor YAML, LVGL displays, LED strips, voice assistant hardware…
HA Integration Dev
Home Assistant custom integration development in Python. Covers customcomponents, DataUpdateCoordinator, configflow, OAuth2, conversation agent, HACS publishing, device registry, entity platforms, services, repair issues, diagnostics, Bluetooth integrations, and multi-coordinator patterns.
Node-RED
Node-RED visual automation flows for Home Assistant. Covers visual automation, flow JSON, trigger-state, api-call-service, function nodes, context storage, timer patterns, error handling, and node-red-contrib-home-assistant-websocket nodes. Use when user mentions "Node-RED", "flow", "visual automation", or…
API Catalog
Reference guide for connecting popular APIs to Home Assistant via Node-RED, YAML, or custom integrations. Covers authentication, endpoints, and complete working examples for: energy APIs (Tibber, Nordpool), weather (SMHI, OpenWeatherMap, yr.no), transport (SL, Trafikverket, Resrobot), smart home clouds (Shelly, Tuya…
HA Dashboard Design
Beautiful, copy-paste-ready Home Assistant dashboard designs with complete CSS themes, card-mod styles, and button-card templates. Nine distinct visual styles: Glassmorphism, Dark Minimal, Material You, Nordic, Neon/Cyberpunk, Warm Home, Soft Pastel, Luxury Gold, and Retro Terminal. Use this skill whenever the user…