Borrowing it
Nothing to install: this file belongs to jpawlowski/hacs.integration_blueprint. 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/jpawlowski/hacs.integration_blueprint/main/.agents/skills/ha-entity-platform/SKILL.mdgit clone --depth 1 https://github.com/jpawlowski/hacs.integration_blueprintWrote 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/jpawlowski/hacs.integration_blueprint/ha-entity-platform)<a href="https://agentmods.dev/skills/jpawlowski/hacs.integration_blueprint/ha-entity-platform"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/ha-entity-platform/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/jpawlowski/hacs.integration_blueprint/ha-entity-platform"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/ha-entity-platform.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.02143 |
| Opus 5 | $0.00108 | $0.01071 |
| Sonnet 5 | $0.00043 | $0.00429 |
| Haiku 4.5 | $0.00022 | $0.00214 |
Grade A, and why
ha-entity-platform 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 10d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add or change an entity platform
Entities are the user-visible surface of the integration. Getting the metadata right at creation time matters more than usual: unique IDs, device classes, and entity IDs are effectively permanent once a user has installed the integration.
Read blueprint.entities.instructions.md first —
it holds the rules this procedure assumes: base-class inheritance and MRO, required EntityDescription fields, the
coordinator-only data rule, availability, device info fields, PARALLEL_UPDATES, and device registry ownership. Copilot
injects it automatically when you edit an entity file; other agents must open it. Python style is in
blueprint.python.instructions.md.
This skill is the procedure and the decisions — it does not restate those rules.
| File | When to read |
|---|---|
references/platform-members.md |
Before implementing a platform — its required members and its one trap |
Before you write code
Clarify — ask the developer if any of this is missing:
- Which platform (
sensor,switch, …) and whether it already exists in the integration. - Which field of
coordinator.databacks the entity, and its unit and value range. - Whether it is a primary entity or a diagnostic/config entity (
EntityCategory). - For writable platforms: which API method performs the write.
Then read the closest existing sibling — for a new sensor that is
custom_components/<domain>/sensor/air_quality.py. Match it rather than inventing a second style.
Layout
Each platform is a package, one entity class per file:
custom_components/<domain>/<platform>/
├── __init__.py # async_setup_entry + aggregated ENTITY_DESCRIPTIONS
└── <group>.py # ENTITY_DESCRIPTIONS + entity class for one logical group
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 182 lines · 216 tokens per session scan A bea8e247c42b
ha-entity-platform is a skill published in the GitHub repository jpawlowski/hacs.integration_blueprint (49 stars, last pushed 3d ago), licensed MIT. It adds 216 tokens to every session and 2,143 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-30.
Other skills, from other repositories
homeassistant
Source-layer Home Assistant guide material preserved behind the runtime guide.
aurora
Aurora Smart Home orchestrator — routing layer for all smart home skills. Use this skill when the user asks ANY smart home question and you need to decide which skill to invoke, or when a task spans multiple skills (e.g., "build a sensor that shows on a dashboard and triggers automations"). Invoke aurora FIRST before…
ESPHome
ESPHome device configuration, firmware, and IoT product development. Covers ESP32, ESP32-S3, ESP32-C3, ESP32-C6, ESP32-H2, ESP32-P4, ESP8266, RP2040, RP2350, nRF52, LibreTiny, Shelly, Sonoff, Tuya, BLE proxy, Matter firmware, Thread, Zigbee, GPIO, sensor YAML, LVGL displays, LED strips, voice assistant hardware…
HA Integration Dev
Home Assistant custom integration development in Python. Covers customcomponents, DataUpdateCoordinator, configflow, OAuth2, conversation agent, HACS publishing, device registry, entity platforms, services, repair issues, diagnostics, Bluetooth integrations, and multi-coordinator patterns.
Node-RED
Node-RED visual automation flows for Home Assistant. Covers visual automation, flow JSON, trigger-state, api-call-service, function nodes, context storage, timer patterns, error handling, and node-red-contrib-home-assistant-websocket nodes. Use when user mentions "Node-RED", "flow", "visual automation", or…
API Catalog
Reference guide for connecting popular APIs to Home Assistant via Node-RED, YAML, or custom integrations. Covers authentication, endpoints, and complete working examples for: energy APIs (Tibber, Nordpool), weather (SMHI, OpenWeatherMap, yr.no), transport (SL, Trafikverket, Resrobot), smart home clouds (Shelly, Tuya…