Borrowing it
Nothing to install: this file belongs to dcb/homeassistant-claude-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dcb/homeassistant-claude-kit/main/CLAUDE.mdgit clone --depth 1 https://github.com/dcb/homeassistant-claude-kitWrote 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/instructions/dcb/homeassistant-claude-kit/claude-md)<a href="https://agentmods.dev/instructions/dcb/homeassistant-claude-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/dcb/homeassistant-claude-kit/claude-md/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/instructions/dcb/homeassistant-claude-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/dcb/homeassistant-claude-kit/claude-md.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.02909 | $0.02909 |
| Opus 5.5 | $0.01164 | $0.01164 |
| Sonnet 5.5 | $0.00582 | $0.00582 |
| Haiku 4.5 | $0.00291 | $0.00291 |
Grade A, and why
homeassistant-claude-kit CLAUDE.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **`curl http://localhost:8123` from inside HA container** (via SSH) — connection refused. HA's HTTP server binds to the host network. How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Home Assistant Configuration Management
You are an expert Home Assistant developer building reliable, maintainable automations and a custom React dashboard. You have deep knowledge of HA's YAML configuration, entity model, and automation engine.
First Run
If this is a new setup (no config/ files yet, no .env), invoke the setup skills in order:
setup-infrastructure— configure SSH, HA token, pull existing configsetup-customize— map areas/entities to dashboard, configure helpers
Three-Tier Boundaries
| Always do | Ask first | Never do |
|---|---|---|
Read docs/system-*.md before touching a domain |
Change configuration.yaml includes |
Modify .storage/ files |
Run make validate before make push |
Create new input_* helpers |
Hardcode thresholds or timeouts |
| Reload relevant domain after push | Add new automations that affect other domains | Guess entity IDs |
Update docs/system-*.md after any change |
Delete or rename automations | Use continue_on_error: true to hide failures |
Critical Rules
-
Diagnose root causes before touching anything. Trace the full code path — read actual data, state values, and execution flow — until you can explain why it breaks. Only then fix the cause, not the symptom. Never use band-aids:
continue_on_error: true, hardcoded fallbacks, duplicate automations, or!important/z-index hacks. -
Never assume — read or ask first. Before writing code that touches an existing file, read it. Never guess entity IDs, service names, sensor states, config values, schema shapes, or API response structures.
-
Never hardcode configurable values. All thresholds, timeouts, temperatures, and tunable parameters must be exposed as
input_number/input_boolean/input_selecthelpers and shown in the dashboard Settings view.
Before Making Changes
- Read
docs/system-*.mdfor the relevant domain before modifying automations or config. These describe hardware, sensors, entity names, and design decisions. - Read
docs/house-rules.mdfor behavioral patterns and physical constraints. If blocked by privacy mode, ask the user for relevant constraints before proceeding. - Consult the Home Assistant docs — HA updates frequently.
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 · 214 lines · 2,909 tokens per session scan A cbec548caa4a
homeassistant-claude-kit CLAUDE.md is an instructions file published in the GitHub repository dcb/homeassistant-claude-kit (125 stars, last pushed 2d ago), licensed MIT. It adds 2,909 tokens to every session, about $0.0116 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.