Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add L3DigitalNet/Claude-Code-Plugins --skill ha-coordinatorgit clone --depth 1 https://github.com/L3DigitalNet/Claude-Code-PluginsWrote 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/l3digitalnet/claude-code-plugins/ha-coordinator)<a href="https://agentmods.dev/skills/l3digitalnet/claude-code-plugins/ha-coordinator"><img src="https://agentmods.dev/badge/skills/l3digitalnet/claude-code-plugins/ha-coordinator/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/l3digitalnet/claude-code-plugins/ha-coordinator"><img src="https://agentmods.dev/badge/skills/l3digitalnet/claude-code-plugins/ha-coordinator.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.00056 | $0.01561 |
| Opus 5.5 | $0.00022 | $0.00624 |
| Sonnet 5.5 | $0.00011 | $0.00312 |
| Haiku 4.5 | $0.00006 | $0.00156 |
Grade A, and why
ha-coordinator 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 1mo 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Home Assistant DataUpdateCoordinator Pattern
The DataUpdateCoordinator is the most important architectural pattern for polling-based integrations. It centralizes data fetching, distributes updates to entities, and handles error/retry logic automatically.
Complete Coordinator Template (2025)
"""DataUpdateCoordinator for {Name}."""
from __future__ import annotations
import logging
from datetime import timedelta
from typing import Any
from homeassistant.config_entries import ConfigEntry
from homeassistant.core import HomeAssistant
from homeassistant.exceptions import ConfigEntryAuthFailed
from homeassistant.helpers.update_coordinator import DataUpdateCoordinator, UpdateFailed
from .const import DEFAULT_SCAN_INTERVAL, DOMAIN
_LOGGER = logging.getLogger(__name__)
class {Name}Coordinator(DataUpdateCoordinator[dict[str, Any]]):
"""Coordinator to manage data fetching."""
config_entry: ConfigEntry
def __init__(self, hass: HomeAssistant, entry: ConfigEntry) -> None:
"""Initialize coordinator."""
super().__init__(
hass,
_LOGGER,
name=DOMAIN,
config_entry=entry,
update_interval=timedelta(
seconds=entry.options.get("scan_interval", DEFAULT_SCAN_INTERVAL)
),
always_update=False, # Safe only if returned data has value-based __eq__ (plain dict/dataclass); use True otherwise
)
# MyClient, AuthenticationError, RateLimitError are placeholders for your integration's API library:
# from my_api import MyClient, AuthenticationError, RateLimitError
self.client = MyClient(
host=entry.data["host"],
username=entry.data["username"],
password=entry.data["password"],
)
async def _async_setup(self) -> None:
"""One-time initialization (Home Assistant 2024.8+).
Called once during async_config_entry_first_refresh() before _async_update_data.
Use for data that doesn't change: device info, serial numbers, capabilities.
Same error handling as _async_update_data (ConfigEntryAuthFailed, UpdateFailed).
"""
self.device_info = await self.client.async_get_device_info()
async def _async_update_data(self) -> dict[str, Any]:
"""Fetch data from the device/API.
Called on every polling cycle.
Raises:
ConfigEntryAuthFailed: Triggers reauth flow (expired/invalid credentials)
UpdateFailed: Marks entities unavailable, logs once, retries on schedule
"""
try:
return await self.client.async_get_data()
except AuthenticationError as err:
raise ConfigEntryAuthFailed("Authentication failed") from err
except ConnectionError as err:
raise UpdateFailed(f"Connection error: {err}") from err
except RateLimitError as err:
# HA 2025.11+: retry_after defers the next scheduled refresh
raise UpdateFailed(
f"Rate limited: {err}",
retry_after=err.retry_after,
) from err
except TimeoutError as err:
raise UpdateFailed(f"Timeout: {err}") from err
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.
- 1mo ago First seen · 191 lines · 56 tokens per session scan A eb572208c209
ha-coordinator is a skill published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (8 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 1,561 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.