ha-recorder

ha-recorder is a skill for Claude Code from L3DigitalNet/Claude-Code-Plugins. It costs 34 tokens per session (1,884 once invoked), scanned A, original, MIT.

A guide for working with the Home Assistant recorder, which stores entity history and statistics in a database. It covers historical data, long-term measurements, and excluding unwanted records.

In plain words
What is it for?
Use it for history queries, energy or other statistics, custom measurements, and recorder exclusions.
Why use it?
It helps control database growth and handle historical data correctly, especially for frequently changing or diagnostic entities.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the home-assistant-dev plugin — 27 skills, 2 commands, 3 agents, 1 hook shipped together

Good fit Use it for history queries, energy or other statistics, custom measurements, and recorder exclusions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/l3digitalnet/claude-code-plugins/ha-recorder
Install

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.

Any agent
npx skills add L3DigitalNet/Claude-Code-Plugins --skill ha-recorder
Clone the repo
git clone --depth 1 https://github.com/L3DigitalNet/Claude-Code-Plugins

Made for: Claude Code.

Or install home-assistant-dev, the plugin that ships this one along with the rest of its 27 skills, 2 commands, 3 agents, 1 hook.

Wrote 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.

agentmods badge for ha-recorder

README.md
[![agentmods](https://agentmods.dev/badge/skills/l3digitalnet/claude-code-plugins/ha-recorder/github.svg)](https://agentmods.dev/skills/l3digitalnet/claude-code-plugins/ha-recorder)
Your own site
<a href="https://agentmods.dev/skills/l3digitalnet/claude-code-plugins/ha-recorder"><img src="https://agentmods.dev/badge/skills/l3digitalnet/claude-code-plugins/ha-recorder/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.

agentmods 80×15 button for ha-recorder

Your own site · 80×15
<a href="https://agentmods.dev/skills/l3digitalnet/claude-code-plugins/ha-recorder"><img src="https://agentmods.dev/badge/skills/l3digitalnet/claude-code-plugins/ha-recorder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,884 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.01884
Opus 5.5 $0.00014 $0.00754
Sonnet 5.5 $0.00007 $0.00377
Haiku 4.5 $0.00003 $0.00188

Measured 1mo ago against content hash 796fc7b9a582, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ha-recorder 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.

plugins/home-assistant-dev/skills/ha-recorder/SKILL.md · 274 lines

How it starts

The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Home Assistant Recorder Integration

Guide for integrations that work with historical data, statistics, and the recorder.

When to Use Recorder Features

  • Statistics: Energy monitoring, long-term trends
  • History exclusion: High-frequency sensors, diagnostic entities
  • Custom statistics: External data sources
  • History queries: Historical analysis features

Excluding from Recorder

Exclude noisy entities from history to reduce database size:

# In your entity class
class MyDiagnosticSensor(SensorEntity):
    """Sensor that shouldn't be recorded."""

    # Disabling an entity keeps it out of the recorder; hiding only removes it from the
    # UI (it is still recorded). For true recorder exclusion, use the recorder config below.
    _attr_entity_registry_enabled_default = False  # Disabled (and not recorded) by default
    _attr_entity_registry_visible_default = False  # Hidden from the UI by default
    _attr_should_poll = True

Or use recorder configuration in the user's config:

# configuration.yaml (user config, not your integration)
recorder:
  exclude:
    entity_globs:
      - sensor.my_integration_debug_*
    domains:
      # `domains` takes entity domains (sensor, switch, ...), not the integration name.
      - sensor

Long-Term Statistics

For sensors that should appear in energy dashboard or statistics graphs:

from homeassistant.components.sensor import (
    SensorDeviceClass,
    SensorEntity,
    SensorStateClass,
)

class MyEnergySensor(SensorEntity):
    """Energy sensor with long-term statistics."""

    _attr_device_class = SensorDeviceClass.ENERGY
    _attr_state_class = SensorStateClass.TOTAL_INCREASING
    _attr_native_unit_of_measurement = "kWh"

    # These attributes enable long-term statistics:
    # - device_class: ENERGY, GAS, WATER, etc.
    # - state_class: MEASUREMENT, TOTAL, TOTAL_INCREASING
    # - unit_of_measurement: Standard units

State Classes

State Class Use Case Example
MEASUREMENT Instantaneous value Temperature
TOTAL Resettable counter Trip odometer
TOTAL_INCREASING Monotonic counter Energy meter

Read the full file on GitHub · 274 lines

Changes

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.

  1. 1mo ago First seen · 274 lines · 34 tokens per session scan A 796fc7b9a582

Subscribe to this mod's changes

ha-recorder is a skill published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (8 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,884 once invoked, about $0.0001 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.