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-repairsnpx skills add L3DigitalNet/Claude-Code-Plugins --skill ha-repairsgit 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.00039 | $0.01354 |
| Opus 5 | $0.00019 | $0.00677 |
| Sonnet 5 | $0.00008 | $0.00271 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
ha-repairs 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 2d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Home Assistant Repair Issues
Repair issues provide actionable notifications to users about problems that require attention. Gold tier IQS requirement.
When to Use Repairs
Use repair issues for:
- Configuration problems the user can fix
- Firmware updates available
- Deprecated features being used
- Missing optional dependencies
- Service disruptions with user action needed
Do NOT use for:
- Transient errors (use logging)
- Entity unavailability (use
availableproperty) - Internal errors (use exceptions)
Basic Implementation
from homeassistant.helpers import issue_registry as ir
# Create an issue
ir.async_create_issue(
hass,
DOMAIN,
"firmware_update_available",
is_fixable=False,
severity=ir.IssueSeverity.WARNING,
translation_key="firmware_update_available",
translation_placeholders={
"current_version": "1.0.0",
"new_version": "2.0.0",
},
)
Severity Levels
from homeassistant.helpers.issue_registry import IssueSeverity
IssueSeverity.CRITICAL # Reserved for HA-internal use — do NOT use in custom integrations
IssueSeverity.ERROR # Something is broken
IssueSeverity.WARNING # Should be addressed soon
Custom integrations should use ERROR or WARNING; CRITICAL is reserved for Home Assistant core.
Issue Types
Non-Fixable Issue
User must take action outside Home Assistant:
ir.async_create_issue(
hass,
DOMAIN,
"device_firmware_outdated",
is_fixable=False,
severity=ir.IssueSeverity.WARNING,
translation_key="device_firmware_outdated",
translation_placeholders={
"device": device_name,
"version": current_version,
},
learn_more_url="https://example.com/firmware-update",
)
Fixable Issue (with Repair Flow)
User can fix directly in Home Assistant:
# In __init__.py or where issue is detected
ir.async_create_issue(
hass,
DOMAIN,
f"reauth_required_{entry.entry_id}",
is_fixable=True,
severity=ir.IssueSeverity.ERROR,
translation_key="reauth_required",
data={"entry_id": entry.entry_id},
)
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.
- 2d ago First seen · 228 lines · 39 tokens per session scan A c9d288745257
ha-repairs is a skill published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 1,354 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.