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/blueprint-scaffold/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/blueprint-scaffold)<a href="https://agentmods.dev/skills/jpawlowski/hacs.integration_blueprint/blueprint-scaffold"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/blueprint-scaffold/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/blueprint-scaffold"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/blueprint-scaffold.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.00211 | $0.02971 |
| Opus 5 | $0.00105 | $0.01486 |
| Sonnet 5 | $0.00042 | $0.00594 |
| Haiku 4.5 | $0.00021 | $0.00297 |
Grade A, and why
blueprint-scaffold 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 11d 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.
a curl dump, a log line, a screenshot of the vendor docs. Entities built against an invented shape look finished and How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold the blueprint into a real integration
This is a one-time task. It runs once, in a repository that has been initialised with initialize.sh but still
contains the blueprint's example platforms. Everything it produces is ordinary integration code afterwards, maintained
with the ha-* skills.
Stop if the repository already has real code. Placeholder identifiers gone and platforms that match a real
device mean scaffolding already happened. Adding an entity to an existing integration is
ha-entity-platform, not this. Migrating a pre-existing integration in is
blueprint-import.
1. Gather the facts — do not start without them
| Fact | Why it decides something |
|---|---|
| What the integration exposes, and to whom | Which platforms survive step 4 |
| Where its values come from | Everything below; see the branch under it |
| A real payload, or the real source | The coordinator's data shape, and every entity's value accessor |
| What drives an update, and how often | iot_class, UPDATE_INTERVAL, whether a listener replaces polling |
| How long one response stays true | Whether the integration can start from cache with no network |
| A stable per-install identifier, if one exists | The config entry unique_id |
Where the values come from is the branch, and it decides which further facts you need.
- A device or an endpoint — HTTP, WebSocket, MQTT, Bluetooth, serial, a vendor SDK. Then you also need the protocol and base URL, the authentication, and whether credentials expire.
- Produced rather than fetched — computed from other entities, a local file or database, a calculation, the clock. There is no API client and no credentials; what you need instead is which sources it reads, what it does when one is missing or the wrong type, and whether the result has to survive a restart.
- Write-only — the integration sends commands and cannot read back. Then the question is what the entity shows
in between, which is
assumed_stateand optimistic state.
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.
- 11d ago First seen · 195 lines · 211 tokens per session scan A 5b3f3940f40d
blueprint-scaffold is a skill published in the GitHub repository jpawlowski/hacs.integration_blueprint (49 stars, last pushed 4d ago), licensed MIT. It adds 211 tokens to every session and 2,971 once invoked, about $0.0011 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 skills, from other repositories
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…
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…