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-planning/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-planning)<a href="https://agentmods.dev/skills/jpawlowski/hacs.integration_blueprint/ha-planning"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/ha-planning/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-planning"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/ha-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 10 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00194 | $0.01760 |
| Opus 5 | $0.00097 | $0.00880 |
| Sonnet 5 | $0.00039 | $0.00352 |
| Haiku 4.5 | $0.00019 | $0.00176 |
Grade A, and why
ha-planning 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 12d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan changes and record decisions
When a plan is required
| Situation | What to do |
|---|---|
| Single feature or fix, up to ~8 files | Just implement it completely; no plan needed |
| Several independent features | Implement one at a time, suggest a commit between each |
| >10 files, or an architectural/structural change | Write a plan and get explicit confirmation first |
| A choice with long-term consequences | Write the plan and record the decision |
Do not start a large refactor because it seems obviously right. The developer decides scope.
A plan can only be as good as the requirements under it. If you cannot state the goal back in one sentence, or the
phases would encode a guess, run ha-grill first — its brief is the input this plan needs.
Writing the plan
Plans are working documents, not deliverables. Put them in .agents/scratch/ — that directory is gitignored and exists for
exactly this. Do not create markdown files elsewhere in the repository without being asked.
Structure:
# Plan: <what and why in one line>
## Goal
<One line: what changes for the user when this is done.>
## Current state
<Bullets. What exists today, with file references, and what specifically is in the way.>
## Approach
<Bullets. The chosen approach, and what you deliberately did not choose.>
## Phases
### Phase 1 — <name>
- **Files:** `custom_components/<domain>/coordinator/base.py`, …
- **Changes:** <specific edits>
- **Verification:** `script/test tests/test_init.py`, and <what to check in the UI>
- **Independently shippable:** yes / no
### Phase 2 — …
## Breaking changes
<None, or: what breaks and the migration path. See ha-breaking-changes.>
## Risks and open questions
<Each one: the question, who answers it, and what it blocks. "None" is a valid section.>
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.
- 12d ago First seen · 159 lines · 194 tokens per session scan A 3cb5b9e08764
ha-planning is a skill published in the GitHub repository jpawlowski/hacs.integration_blueprint (49 stars, last pushed 4d ago), licensed MIT. It adds 194 tokens to every session and 1,760 once invoked, about $0.0010 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…