Home Assistant is open-source home automation software that lets people control devices and actions locally through a modular system. It is used by home-automation enthusiasts and DIY users, often on a Raspberry Pi or local server; the catalogue entries support operating or developing its integrations and codebase.
Borrowing it
Nothing to install: this file belongs to home-assistant/core. 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/home-assistant/core/dev/.claude/skills/custom-integration-sources/SKILL.mdgit clone --depth 1 https://github.com/home-assistant/coreWrote 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/home-assistant/core/custom-integration-sources)<a href="https://agentmods.dev/skills/home-assistant/core/custom-integration-sources"><img src="https://agentmods.dev/badge/skills/home-assistant/core/custom-integration-sources/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/home-assistant/core/custom-integration-sources"><img src="https://agentmods.dev/badge/skills/home-assistant/core/custom-integration-sources.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.00073 | $0.02507 |
| Opus 5.5 | $0.00029 | $0.01003 |
| Sonnet 5.5 | $0.00015 | $0.00501 |
| Haiku 4.5 | $0.00007 | $0.00251 |
Grade A, and why
custom-integration-sources 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 7d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Custom integration sources
A local snapshot of every repository in the HACS default integration list, at the HEAD of each default branch. Each repo is a blobless git clone: full commit history, with file contents downloaded only when needed. Its sparse checkout holds what HACS installs (custom_components/, plus the root hacs.json), minus common binary file types (~3.3 GB for ~3,250 repos, about 1.9 GB of it git history). Repos with content_in_root set in hacs.json (or with no custom_components/ at all) are checked out whole.
The copy is made by script/sync_custom_integrations.py. Layout: <copy>/<owner>/<repo>/..., each a git repository with an origin remote, and <copy>/.state.json mapping each owner/repo to the synced commit SHA under repos. Repos can be opened in an editor for blame and GitHub permalinks.
Locate the copy
- Use the directory the user names, if any. Otherwise use
.custom_integration_sources/in the main worktree, which all git worktrees share:"$(dirname "$(git rev-parse --path-format=absolute --git-common-dir)")/.custom_integration_sources". In a linked worktree, use that copy; never create a second one there. - A directory is a valid copy only if its
.state.jsonhas"format": "custom-integration-sources/1". - If there is no valid copy, ask the user where theirs is, or whether to create one (a first sync takes about 5 minutes), or whether a quick GitHub code search is enough (see below). Never start a sync unprompted.
- Before offering a first sync, check free space on the destination's filesystem (
df -hon the destination's parent directory) and tell the user the copy needs about 3.5 GB, so they can pick another location with--destor free up space first. - Before searching, state how old the snapshot is, from
synced_atin.state.json: the time the last full sync without failures finished. Targeted, failed or interrupted runs don't update it, so never use the file's modification time. Ifsynced_atis missing, say the age is unknown. Do not refresh the copy unless the user asks; suggest a refresh if it is more than a few days old, or of unknown age.
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.
- 7d ago First seen · 92 lines · 73 tokens per session scan A 7fc523b8bffd
custom-integration-sources is a skill published in the GitHub repository home-assistant/core (91,801 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 2,507 once invoked, about $0.0003 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-10-22.
Other skills, from other repositories
iot-skills
Use when developing IoT solutions — Raspberry Pi Pico (RP2040) GPIO/I2C/Wi-Fi/MQTT/sensors in MicroPython, building low-code data flows with Node-RED, running a local-first home automation platform with Home Assistant, or compiling ESP32/ESP8266 firmware from YAML with ESPHome. Index of 4 skills: KE3036 Keyes Pico…
iot-developer
Expert in IoT development, microcontrollers, sensors, and MQTT protocols.
edge-iot
Edge computing, IoT protocols, and embedded systems integration.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
config-loading-precedence
How Xberg resolves config: CLI and server/MCP precedence, file walk-up, inline JSON, overrides. Use when adding a setting or one does not take effect.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.