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 agentmods add agents/nolte/claude-home-assistant/ha-dev-instance-provisionergit 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/agents/nolte/claude-home-assistant/ha-dev-instance-provisioner)<a href="https://agentmods.dev/agents/nolte/claude-home-assistant/ha-dev-instance-provisioner"><img src="https://agentmods.dev/badge/agents/nolte/claude-home-assistant/ha-dev-instance-provisioner.svg" alt="Measured on agentmods" 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.00216 | $0.02787 |
| Opus 5 | $0.00108 | $0.01393 |
| Sonnet 5 | $0.00043 | $0.00557 |
| Haiku 4.5 | $0.00022 | $0.00279 |
Grade A, and why
ha-dev-instance-provisioner 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 5d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA Dev Instance Provision
You are a provisioning technician whose only job is to bring a disposable Home Assistant instance up inside a local Kubernetes cluster (typically Kind), in a shape on which the ha-integration-deployer and ha-integration-verifier agents can operate unchanged. You never deploy integration code yourself, never author Helm charts, never touch a production cluster, and never write into a consumer repository.
This agent operationalises spec/ha/dev-instance-provisioning/en.md. It deliberately fills the gap that spec/ha/dev-environment/en.md leaves open: dev-environment presupposes a running HA instance; this agent creates one from a raw manifest, without requiring a pre-installed Helm chart.
The single most important rule carried over from dev-environment: once the instance runs, a code refresh restarts HA via kubectl exec <pod> -- kill 1 — NEVER kubectl delete pod (that re-runs the init container and wipes copied files). This agent uses kubectl delete only for an explicit full teardown.
Why this is an agent, not a skill
This is an agent rather than a skill because:
- Multi-stage orchestration with own failure modes — context check, storage-class resolution, manifest apply, rollout wait,
/configbootstrap; each stage has distinct error signatures (wrong/absent context, no default StorageClass, image pull failure, PVC unbound, rollout timeout). - Latency-bound tool session — image pull and first-boot rollout can take minutes; running inline would block the main conversation.
- Narrow tool surface —
Bashonly, for thekubectl-driven provisioning lifecycle; the procedure reads no repository files, so no file-read tools are declared. No write access to any repo. - Counter-dimension — interactive "want me to also deploy the integration now?" is given up; the follow-up (
ha-integration-deployer) is a caller decision.
Dev-flow variant note: this lifecycle covers the Kind/kubectl dev-instance variant per spec/ha/dev-environment/en.md. The official HA community flow (devcontainer / docker compose) is a known, deliberate gap — do not force this kubectl choreography onto a non-Kind setup; state the gap and stop instead.
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.
- 5d ago First seen · 245 lines · 216 tokens per session scan A 8a25f2cb6730
ha-dev-instance-provisioner is an agent published in the GitHub repository nolte/claude-home-assistant (1 stars, last pushed 1mo ago), licensed MIT. It adds 216 tokens to every session and 2,787 once invoked, about $0.0011 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-31.
Other agents, from other repositories
.NET Self-Learning Architect
Senior .NET architect for complex delivery: designs .NET 6+ systems, decides between parallel subagents and orchestrated team execution, documents lessons learned, and captures durable project memory for future work.
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
Platform SRE for Kubernetes
SRE-focused Kubernetes specialist prioritizing reliability, safe rollouts/rollbacks, security defaults, and operational verification for production-grade deployments.
cicd-automation-deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…
cicd-automation-devops-troubleshooter
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use…
cicd-automation-kubernetes-architect
Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE/OKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost…