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-testing/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-testing)<a href="https://agentmods.dev/skills/jpawlowski/hacs.integration_blueprint/ha-testing"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/ha-testing/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-testing"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/ha-testing.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.00194 | $0.02137 |
| Opus 5 | $0.00097 | $0.01069 |
| Sonnet 5 | $0.00039 | $0.00427 |
| Haiku 4.5 | $0.00019 | $0.00214 |
Grade A, and why
ha-testing 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing
Home Assistant tests are integration tests by nature: you load a real config entry into a real hass instance and
assert on hass.states — not on Python objects.
Read blueprint.tests.instructions.md first — it
holds the rules: directory mirroring, pytest markers, which fixtures to define, the core-interface rule, registry
assertions, what to mock and what never to mock, the full command list, and the do/don't list. This skill is the
scaffolding and the judgement calls.
When a test is required
- Behavioural change, bug fix, or regression → add a proportionate test.
- Documentation-only, formatting-only, or anything that cannot affect runtime → no test needed.
- If a test is impractical (needs real hardware, non-deterministic timing), say so explicitly and describe the residual risk. Do not silently skip it, and never claim coverage that does not exist.
Bootstrap: tests/conftest.py
The suite currently has no conftest.py. Custom integrations are not loaded by default in tests, so the first thing
any new test file needs is this — create it once:
"""Shared fixtures for <domain> tests."""
from collections.abc import Generator
from unittest.mock import AsyncMock, patch
import pytest
from pytest_homeassistant_custom_component.common import MockConfigEntry
from custom_components.<domain>.const import DOMAIN
from homeassistant.const import CONF_PASSWORD, CONF_USERNAME
from homeassistant.core import HomeAssistant
@pytest.fixture(autouse=True)
def auto_enable_custom_integrations(enable_custom_integrations: None) -> None:
"""Load the custom integration in every test."""
@pytest.fixture
def mock_config_entry() -> MockConfigEntry:
"""Return a config entry for the integration."""
return MockConfigEntry(
domain=DOMAIN,
title="Example Device",
data={CONF_USERNAME: "test-user", CONF_PASSWORD: "test-password"},
unique_id="test-unique-id",
)
@pytest.fixture
def mock_api_client() -> Generator[AsyncMock]:
"""Patch the API client with a mock that returns fixture data."""
with patch(
"custom_components.<domain>.{ClassPrefix}ApiClient",
autospec=True,
) as client_class:
client = client_class.return_value
client.async_get_data.return_value = {"model": "Blueprint", "title": "ok"}
yield client
@pytest.fixture
async def init_integration(
hass: HomeAssistant,
mock_config_entry: MockConfigEntry,
mock_api_client: AsyncMock,
) -> MockConfigEntry:
"""Set up the integration and return the loaded entry."""
mock_config_entry.add_to_hass(hass)
assert await hass.config_entries.async_setup(mock_config_entry.entry_id)
await hass.async_block_till_done()
return mock_config_entry
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 · 229 lines · 194 tokens per session scan A 56af1c6e7b80
ha-testing is a skill published in the GitHub repository jpawlowski/hacs.integration_blueprint (49 stars, last pushed 2d ago), licensed MIT. It adds 194 tokens to every session and 2,137 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
bat-story-eval
Compare MCP tool behavior between target and baseline versions using pre-built and custom stories with diff-based triage.
bat-adhoc
Run bot acceptance tests to validate MCP tools work correctly from a real AI agent's perspective. Use when testing PRs, detecting regressions, or verifying tool changes end-to-end with Claude/Gemini CLIs.
homeassistant
Source-layer Home Assistant guide material preserved behind the runtime guide.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.