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 nolte/claude-home-assistant --skill ha-integration-solutiongit clone --depth 1 https://github.com/nolte/claude-home-assistantWrote 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/nolte/claude-home-assistant/ha-integration-solution)<a href="https://agentmods.dev/skills/nolte/claude-home-assistant/ha-integration-solution"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-integration-solution/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/nolte/claude-home-assistant/ha-integration-solution"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-integration-solution.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.00208 | $0.04909 |
| Opus 5.5 | $0.00083 | $0.01964 |
| Sonnet 5.5 | $0.00042 | $0.00982 |
| Haiku 4.5 | $0.00021 | $0.00491 |
Grade A, and why
ha-integration-solution 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA Integration Solution
Spec: spec/claude/ha-integration-solution/en.md (EN canonical) / spec/claude/ha-integration-solution/de.md (DE translation).
This skill is the front door to the Python custom-integration backend cluster — the integration-side counterpart to ha-automation-solution. It does not generate any artifact itself — it decomposes the requirement, plans the dependency-ordered combination, and dispatches the owning individual skills, each of which owns its generation and spec conformance.
Why this is a skill, not an agent
- Plan-before-generate gate — the skill plan must be presented and explicitly approved before any generation; that human-visible gate is core to the contract and an agent's fire-and-forget shape would lose it.
- Mid-flow interactivity — clarifying questions (protocol, auth type, entity domains, quality features), plan confirmation, and the "this is actually a YAML automation, not an integration" decision are per-run dialogues.
- Orchestrator that dispatches other skills — the skill-orchestrates-skill default (see
skill-vs-agent) keeps the entry point in skill form, likeha-automation-solutiondispatching its authoring skills. - Counter-dimension considered: the per-building-block generation could run as parallel agents, but the plan approval and the
domain/entity_idthreading must stay visible in the user's context; skill wins.
When this skill activates
Use this skill when the user describes a device/cloud/API integration result that likely needs more than one building block, and should not have to know which integration skill produces what — "build an integration for X", "integrate my Acme thermostat over its cloud API", "baue mir eine Integration für …".
When NOT to activate
- a single clear augment (one config-flow pattern, one coordinator, one platform, one diagnostics enrichment) → let the owning skill activate directly
- a pure YAML automation/helper/template/blueprint solution (no own protocol, no config flow) →
ha-automation-solution - a Lovelace frontend card →
ha-lovelace-card-scaffold(and the Lovelace skill family) - deploying/verifying against a running HA instance as a standalone task → not an activation reason; deploy/verify happens only inside the opt-in
deploy_readylifecycle phase (§5) of a build run, behind a second gate, via theha-integration-deployer/ha-integration-verifieragents
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 · 190 lines · 208 tokens per session scan A 651ee103282a
ha-integration-solution is a skill published in the GitHub repository nolte/claude-home-assistant (1 stars, last pushed 1mo ago), licensed MIT. It adds 208 tokens to every session and 4,909 once invoked, about $0.0008 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-31.
Other skills, from other repositories
sglang
Fast structured generation and serving for LLMs with RadixAttention prefix caching. Use for JSON/regex outputs, constrained decoding, agentic workflows with tool calls, or when you need 5× faster inference than vLLM with prefix sharing. Powers 300,000+ GPUs at xAI, AMD, NVIDIA, and LinkedIn.
technical-troubleshooting
Provide setup, troubleshooting, and maintenance guidance. Use when the user reports a device that won't power on, connectivity issues, setup questions, overheating, or maintenance concerns.
mqtt-development
Best practices and guidelines for MQTT messaging in IoT and real-time communication systems.
agent-django-fastapi-expert
Specialist subagent: Django ORM, Django REST Framework, FastAPI async patterns, and Pydantic v2 specialist. Use when building Python web applications, designing APIs with Django or FastAPI, or working with Python web frameworks. Trigger phrases: Django, FastAPI, DRF, Django REST Framework, Pydantic, ORM, queryset…
microservices-architecture
Microservices architecture patterns and best practices. Use when designing distributed systems, breaking down monoliths, or implementing service communication.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.