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 nolte/claude-home-assistant --skill ha-derived-sensor-authorgit clone --depth 1 https://github.com/nolte/claude-home-assistantWrote 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/nolte/claude-home-assistant/ha-derived-sensor-author)<a href="https://agentmods.dev/skills/nolte/claude-home-assistant/ha-derived-sensor-author"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-derived-sensor-author/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/nolte/claude-home-assistant/ha-derived-sensor-author"><img src="https://agentmods.dev/badge/skills/nolte/claude-home-assistant/ha-derived-sensor-author.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.00217 | $0.02290 |
| Opus 5 | $0.00109 | $0.01145 |
| Sonnet 5 | $0.00043 | $0.00458 |
| Haiku 4.5 | $0.00022 | $0.00229 |
Grade A, and why
ha-derived-sensor-author 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HA Derived Sensor Author
Spec: spec/claude/ha-derived-sensor-author/en.md (EN canonical) / spec/claude/ha-derived-sensor-author/de.md (DE translation).
Why this is a skill, not an agent
- Human-visible authoring surface — the user describes the derived value they need and reads back the YAML and the conformance report; a skill keeps this on the visible command surface, like the sibling author/scaffold skills.
- Mid-flow interactivity — integration selection and the delimitation redirect (rate vs. smoothing vs. integral; threshold vs. trend) are per-run dialogues the user approves before generation.
- Bounded, inline generation — a single sensor block is small enough to generate inline.
- Counter-dimension considered: the draft→validate loop could be an agent, but the integration choice and the runtime-dependency notes belong in the user's working context; skill wins.
When this skill activates
Use this skill to author one derived/statistical helper sensor from a described intent: bayesian, derivative, filter, min_max, statistics, threshold, trend, history_stats, integration (Riemann), utility_meter, or group.
When NOT to activate
- the generic
template:integration (free-form Jinja sensors) →ha-automation-author - a stateful helper (
input_*,counter,timer,schedule) →ha-helper-scaffold - an automation, script, or scene →
ha-automation-author - a real sensor from your own integration →
ha-integration-scaffold - a blueprint →
ha-blueprint-scaffold - deploying/importing into a running HA instance → out of scope
Hard rules
- One sensor, one integration, one run. No batches.
- Intent is mandatory. Optional fields fall back to documented defaults stated in the output.
- Read the topic spec first. Read the matching
ha-automation/<topic>spec before generating. - Right integration, with delimitation. Rate →
derivative, smoothing →filter, time-integral →integration; momentary aggregate →min_max, time aggregate →statistics, past-window →history_stats; momentary threshold →threshold, direction →trend. A free formula →template(viaha-automation-author); a stored value →ha-helper-scaffold. Redirect rather than forcing the wrong one. - A source entity is required for every integration except
bayesian(which works offobservations). No source → ask, don't guess. - Set the math-bearing parameter correctly per the topic spec — never
prob_given_*of 0/1;unit_timedeliberate;derivativeon a non-negative source needsstate_class: total_increasing;filterwindow_sizenot a needlessly large integer;min_maxsources share one unit;statisticsstate_characteristicmatches source type;thresholdlower < upperwithhysteresison noisy sources;trendmin_gradientin units per second;history_statsexactly two ofstart/end/duration;utility_metera monotonic source withcycleorcron(not both);groupmodern per-domain, deliberateall. - Type the sensor and guard the source. Correct
sensor/binary_sensor,device_class/state_class; robust against sourceunavailable/unknown. Name perspec/ha/naming-conventions/en.md. - Never overwrite an existing sensor with the same
unique_id. Verify HA internals against the official docs (seespec/ha/upstream-docs-verification/en.md).
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 · 121 lines · 217 tokens per session scan A f0c8fa49a813
ha-derived-sensor-author is a skill published in the GitHub repository nolte/claude-home-assistant (1 stars, last pushed 1mo ago), licensed MIT. It adds 217 tokens to every session and 2,290 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-31.
Other skills, from other repositories
embedded-iot
Embedded systems firmware, microcontrollers (ESP32, STM32, Arduino, Raspberry Pi), RTOS (FreeRTOS, Zephyr), IoT protocols (MQTT, CoAP, BLE), bare-metal C/C++, and hardware peripheral interfaces (I2C, SPI, UART, GPIO). Use when developing firmware, working with microcontrollers, or building IoT devices.
spark-environment-setup
Set up a working ML training/inference environment on NVIDIA DGX Spark (GB10, aarch64, CUDA 13). Use when installing PyTorch/Unsloth/TRL/vLLM on DGX Spark, hitting libcudart or wheel-ABI errors on aarch64, or choosing between NGC containers and bare pip installs.
spark-training-gotchas
Preflight and diagnose the ten known failure modes for ML training on NVIDIA DGX Spark. Use when a training run on DGX Spark fails to start, OOMs below the 128GB limit, slows down mid-run, or before any multi-hour training job on GB10.
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
stride-analysis-patterns
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…