Borrowing it
Nothing to install: this file belongs to homeassistant-ai/skills. 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/homeassistant-ai/skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/homeassistant-ai/skillsWrote 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/homeassistant-ai/skills/claude-md)<a href="https://agentmods.dev/instructions/homeassistant-ai/skills/claude-md"><img src="https://agentmods.dev/badge/instructions/homeassistant-ai/skills/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/homeassistant-ai/skills/claude-md"><img src="https://agentmods.dev/badge/instructions/homeassistant-ai/skills/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.01944 | $0.01944 |
| Opus 5 | $0.00972 | $0.00972 |
| Sonnet 5 | $0.00389 | $0.00389 |
| Haiku 4.5 | $0.00194 | $0.00194 |
Grade A, and why
skills 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 9d 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.
- UI renames, terminology, and default changes appear only in release blog posts, not core source: `source/_posts/<date>-release-<version>.markdown` in the docs repo (e.g. `2026-08-05-release-20268.markdown`). Use `gh ap How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Repo Layout
Eval cases live in a top-level evals/<case>/case.yaml, not under skills/. claude plugin eval rejects any eval directory whose first segment names a loaded component directory
(commands, skills, agents, hooks, themes, output-styles, monitors, workflows,
bin) — and rejects it softly: it warns, falls back to the default evals/, and finds
nothing, so cases in the wrong place silently never run. evals/ at the plugin root is the
default and needs no experimental.evals key.
SKILL.md is in context on every trigger; references/ load only when read. That is why
SKILL.md body size is capped and why domain-niche content belongs in a reference file behind
a single routing row, not in the always-loaded table.
Skill Format
Every skill is a SKILL.md with name/description frontmatter. Full authoring constraints: CONTRIBUTING.md. The one CI cannot catch:
metadata.versionmust be"0"on new skills — do not edit manually; CI assigns the real version on merge and syncs it into.claude-plugin/plugin.json(.version) and.claude-plugin/marketplace.json(.metadata.version) — three files, one source of truthdescriptionis capped at 1024 chars and runs close to it — measure the parsed length before adding trigger/symptom bullets:uvx --from skills-ref agentskills read-properties skills/<skill-name> | jq '.description | length'
Skill Authoring Principles
The wording of these content-quality principles is mirrored in CONTRIBUTING.md
(contributors); each file also carries guidance the other omits. When you change a shared
principle, change both — they have drifted before.
- Context window conservation — keep what is HA-specific, cut general programming advice; the test is the content itself, not whether a given model already knows it (skills run on frontier and small local models alike)
- Conciseness — provide patterns and quick-reference tables, not tutorials
- Consistent terminology — one term per concept throughout a skill; contrasting code blocks are
# WRONG — why/# RIGHT — why(emoji only in table status columns). A renamed HA term uses the new name and cites the old one with its version ("named Developer Tools before 2026.8") — never a bare swap, since readers on older releases still see the old label - Symptom-based triggering — the
descriptionfrontmatter should describe observable agent behaviors that signal the skill is needed - No tool names — reference HA REST APIs and concepts, never specific MCP tool names (e.g.
ha_rename_entity); tool names vary by agent setup
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.
- 9d ago First seen · 100 lines · 1,944 tokens per session scan A f40719162035
skills CLAUDE.md is an instructions file published in the GitHub repository homeassistant-ai/skills (732 stars, last pushed 4d ago), licensed MIT. It adds 1,944 tokens to every session, about $0.0097 per session on Opus 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
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.
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).
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.