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 issue-to-pr-resolvergit 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/issue-to-pr-resolver)<a href="https://agentmods.dev/skills/homeassistant-ai/ha-mcp/issue-to-pr-resolver"><img src="https://agentmods.dev/badge/skills/homeassistant-ai/ha-mcp/issue-to-pr-resolver/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/issue-to-pr-resolver"><img src="https://agentmods.dev/badge/skills/homeassistant-ai/ha-mcp/issue-to-pr-resolver.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.00085 | $0.01199 |
| Opus 5.5 | $0.00034 | $0.00480 |
| Sonnet 5.5 | $0.00017 | $0.00240 |
| Haiku 4.5 | $0.00009 | $0.00120 |
Grade A, and why
issue-to-pr-resolver 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- issue-to-pr-resolver — 100% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue-to-PR Resolver
Implement GitHub issue #$ARGUMENTS in homeassistant-ai/ha-mcp end-to-end.
Phase 1: Setup
Read the issue:
gh issue view "$ARGUMENTS" --repo homeassistant-ai/ha-mcp --json title,body,labels,comments,author
Create a worktree from repo root:
cd "$(git rev-parse --show-toplevel)"
git checkout master && git pull origin master
git worktree add "worktree/issue-$ARGUMENTS" -b "feature/issue-$ARGUMENTS"
git -C "worktree/issue-$ARGUMENTS" submodule update --init --recursive
cd "worktree/issue-$ARGUMENTS"
Phase 2: Implement
- Analyze codebase structure and patterns before writing code
- Follow project conventions (see
AGENTS.mdfor patterns, naming, error handling) - Write tests — all new MCP tools in
src/ha_mcp/tools/need E2E tests - Make atomic, well-described commits using conventional commit prefixes
Philosophy: Work autonomously. Don't ask about every small decision. Fix unrelated test failures encountered. Document all choices for the final summary.
If a non-obvious choice has significant consequences, present the available options to the user and let them choose.
Phase 3: Create PR
Write the PR body to local/pr-body-$ARGUMENTS.md first. local/ is git-ignored, so a new worktree does not have it; create it with mkdir -p local if it does not exist. Build the body from .github/pull_request_template.md: keep its headings, put Closes #$ARGUMENTS and the description under ## What does this PR do?, and delete ## Future improvements unless the user has confirmed work to defer. Then push and create the PR:
git push -u origin "feature/issue-$ARGUMENTS"
PR_NUMBER=$(gh pr create --draft \
--repo homeassistant-ai/ha-mcp \
--title "<descriptive title>" \
--body-file "local/pr-body-$ARGUMENTS.md" | grep -oE '[0-9]+$')
Wait for CI:
gh pr checks "$PR_NUMBER" --repo homeassistant-ai/ha-mcp --watch
Before marking ready (gh pr ready), update the PR description to reflect all changes made.
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 · -3 lines 0d6f96689ac8
- 1mo ago Changed 3fb43107488e
- 1mo ago First seen · 114 lines · 85 tokens per session scan A 97fc9693f185
issue-to-pr-resolver is a skill published in the GitHub repository homeassistant-ai/ha-mcp (5,280 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 1,199 once invoked, about $0.0003 per session on Opus 5.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
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
resolve-drive-pr
Drive an open PR through Polly/OCR, validation, and maintainer handoff.
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
describe-pr
Only use when the user explicitly invokes this skill by name.
feature-publish
Commit the feature, write the PR body, publish in the selected mode, and drive the PR.