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-hacsnpx skills add L3DigitalNet/Claude-Code-Plugins --skill ha-hacsgit 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-hacs)<a href="https://agentmods.dev/skills/l3digitalnet/claude-code-plugins/ha-hacs"><img src="https://agentmods.dev/badge/skills/l3digitalnet/claude-code-plugins/ha-hacs.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00956 |
| Opus 5 | $0.00018 | $0.00478 |
| Sonnet 5 | $0.00007 | $0.00191 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
ha-hacs 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 4d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HACS Metadata Guide
HACS (Home Assistant Community Store) is the standard distribution method for custom integrations.
Repository Structure
my-integration/
├── custom_components/
│ └── {domain}/
│ ├── __init__.py
│ ├── manifest.json # HA manifest (required)
│ ├── config_flow.py
│ └── ...
├── hacs.json # HACS metadata (required)
├── README.md # Documentation (required)
├── LICENSE # License file (recommended)
└── .github/
└── workflows/
└── validate.yml # HACS validation workflow
manifest.json Requirements
HACS requires these fields in manifest.json:
{
"domain": "my_integration",
"name": "My Integration",
"version": "1.0.0",
"codeowners": ["@your-github-username"],
"documentation": "https://github.com/user/repo",
"issue_tracker": "https://github.com/user/repo/issues",
"config_flow": true,
"integration_type": "hub",
"iot_class": "local_polling",
"requirements": ["my-library==1.0.0"]
}
Required for HACS:
domain— Must match folder namename— Display nameversion— Valid semver (X.Y.Z); required in manifest.json for HACS custom integrations, but must be omitted for HA core integrationscodeowners— At least one GitHub usernamedocumentation— URL to docsissue_tracker— URL for bug reports
The list above is the HACS-metadata-required set. Separately, integration_type and iot_class are required by hassfest, and the HACS validation action runs hassfest — so a HACS-targeting repo needs them too (iot_class must be one of the accepted values; integration_type is validated strictly when present).
hacs.json Configuration
Create hacs.json in repository root:
{ "name": "My Integration", "homeassistant": "2025.1.0" }
Common hacs.json Options
| Key | Type | Required | Description |
|---|---|---|---|
name |
string | Yes | Display name in HACS |
homeassistant |
string | No | Minimum HA version (e.g., "2025.1.0") |
hacs |
string | No | Minimum HACS version |
content_in_root |
bool | No | Set true if files not in custom_components/ |
zip_release |
bool | No | Set true if using zipped releases |
filename |
string | No | Main file name (for zip_release) |
render_readme |
bool | No | Render the README in the HACS info panel |
country |
string/array | No | ISO country codes (e.g., "US" or ["US", "CA"]) |
hide_default_branch |
bool | No | Hide default branch from version list |
persistent_directory |
string | No | Directory to preserve during updates |
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.
- 4d ago First seen · 105 lines · 36 tokens per session scan A 869fefe94e71
ha-hacs is a skill published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (6 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 956 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…