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 agentmods add skills/l3digitalnet/claude-code-plugins/ha-recordernpx skills add L3DigitalNet/Claude-Code-Plugins --skill ha-recordergit clone --depth 1 https://github.com/L3DigitalNet/Claude-Code-PluginsWhat 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 | $0.00034 | $0.01884 |
| Opus 5 | $0.00017 | $0.00942 |
| Sonnet 5 | $0.00007 | $0.00377 |
| Haiku 4.5 | $0.00003 | $0.00188 |
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 3d 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 — 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 |
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.
- 3d ago First seen · 274 lines · 34 tokens per session scan A 796fc7b9a582
ha-recorder is a skill published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (6 stars, last pushed 4d ago), licensed MIT. It adds 34 tokens to every session and 1,884 once invoked, about $0.0002 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
bigquery-ai-ml
Leverages BigQuery's built-in machine learning and GenAI capabilities for advanced data analytics. Use when you need to write SQL queries that perform time-series forecasting, predict values, detect outliers or anomalies, find key drivers, perform semantic search or vector search, classify text, calculate similarity…
moderator-page-migration
Port a moderator page from the main Next.js app (src/pages/moderator/) into apps/moderator. Use when asked to migrate, move or cut over a /moderator/ page to the spoke, or to port its tRPC procedures and Prisma services to SvelteKit loads/actions and Kysely.
prisma-upgrade-v7
Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on "upgrade to prisma 7", "prisma 7 migration", "prisma-client generator", "driver adapter required".
ddia-systems
Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "which database should I use", "SQL or NoSQL", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID…
sqlitecpp-update-sqlite
How to update the bundled SQLite3 amalgamation (sqlite3/sqlite3.c and sqlite3.h), the Meson wrap, README.md, and CHANGELOG.md. Use when upgrading SQLite, refreshing the vendored amalgamation, or bumping the sqlite3 wrap.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, FK…