Borrowing it
Nothing to install: this file belongs to philippb/claude-homeassistant. 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/philippb/claude-homeassistant/main/CLAUDE.mdgit clone --depth 1 https://github.com/philippb/claude-homeassistantWrote 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/philippb/claude-homeassistant/claude-md)<a href="https://agentmods.dev/instructions/philippb/claude-homeassistant/claude-md"><img src="https://agentmods.dev/badge/instructions/philippb/claude-homeassistant/claude-md.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.02085 | $0.02085 |
| Opus 5 | $0.01043 | $0.01043 |
| Sonnet 5 | $0.00417 | $0.00417 |
| Haiku 4.5 | $0.00209 | $0.00209 |
Grade B, and why
claude-homeassistant CLAUDE.md scanned grade B 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 8d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
1. Verify SSH key permissions: `chmod 600 ~/.ssh/your_key` How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Home Assistant Configuration Management
This repository manages Home Assistant configuration files with automated validation, testing, and deployment.
Before Making Changes
Always consult the latest Home Assistant documentation at https://www.home-assistant.io/docs/ before suggesting configurations, automations, or integrations. HA updates frequently and syntax/features change between versions.
Project Structure
config/- Contains all Home Assistant configuration files (synced from HA instance)tools/- Validation and testing scriptsvenv/- Python virtual environment with dependenciestemp/- Temporary directory for Claude to write and test code before moving to final locationsMakefile- Commands for pulling/pushing configuration.claude-code/- Project-specific Claude Code settings and hookshooks/- Validation hooks that run automaticallysettings.json- Project configuration
Rsync Architecture
This project uses two separate exclude files for different sync operations:
| File | Used By | Purpose |
|---|---|---|
.rsync-excludes-pull |
make pull |
Less restrictive |
.rsync-excludes-push |
make push |
More restrictive |
Why separate files?
make pulldownloads most files including.storage/(excluding sensitive auth files) for local referencemake pushwrites never overwrites HA's runtime state (.storage/)
What This Repo Can and Cannot Manage
SAFE TO MANAGE (YAML files)
automations.yaml- Automation definitionsscenes.yaml- Scene definitionsscripts.yaml- Script definitionsconfiguration.yaml- Main configurationsecrets.yaml- Secret values
NEVER MODIFY LOCALLY (Runtime State)
These files in .storage/ are managed by Home Assistant at runtime. Local modifications will be overwritten by HA on restart or ignored entirely.
Entity/Device Changes (Manual Only)
Do not change entities or devices programmatically from this repo. If changes are needed, make them manually in the Home Assistant UI:
- Settings → Devices & Services → Entities → Edit
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.
- 8d ago First seen · 225 lines · 2,085 tokens per session scan B 1e94fa202872
claude-homeassistant CLAUDE.md is an instructions file published in the GitHub repository philippb/claude-homeassistant (387 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 2,085 tokens to every session, about $0.0104 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.