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 L3DigitalNet/Claude-Code-Plugins --skill ha-documentationgit 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-documentation)<a href="https://agentmods.dev/skills/l3digitalnet/claude-code-plugins/ha-documentation"><img src="https://agentmods.dev/badge/skills/l3digitalnet/claude-code-plugins/ha-documentation/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/l3digitalnet/claude-code-plugins/ha-documentation"><img src="https://agentmods.dev/badge/skills/l3digitalnet/claude-code-plugins/ha-documentation.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.00043 | $0.01285 |
| Opus 5.5 | $0.00017 | $0.00514 |
| Sonnet 5.5 | $0.00009 | $0.00257 |
| Haiku 4.5 | $0.00004 | $0.00128 |
Grade A, and why
ha-documentation 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.
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Home Assistant Integration Documentation
Guide for creating comprehensive documentation for custom integrations.
Documentation Files
| File | Purpose | Location |
|---|---|---|
| README.md | GitHub landing page | Repository root |
| info.md | HACS description | Repository root |
| docs/*.md | Extended docs | Optional |
README.md Template
# {Integration Name}
[](https://github.com/hacs/integration) [](https://github.com/{username}/{repo}/releases)
{Brief description of what the integration does.}
## Features
- Feature 1
- Feature 2
- Feature 3
## Installation
### HACS (Recommended)
1. Open HACS in Home Assistant
2. Click "Integrations"
3. Click ⋮ → "Custom repositories"
4. Add `https://github.com/{username}/{repo}` as category "Integration"
5. Click "{Integration Name}" → "Download"
6. Restart Home Assistant
### Manual
1. Download the latest release
2. Copy `custom_components/{domain}` to your `custom_components` folder
3. Restart Home Assistant
## Configuration
1. Go to **Settings** → **Devices & Services**
2. Click **+ Add Integration**
3. Search for "{Integration Name}"
4. Follow the setup wizard
### Configuration Options
| Option | Default | Description |
| -------- | -------- | --------------------- |
| Host | Required | Device IP or hostname |
| Username | Required | Login username |
| Password | Required | Login password |
### Advanced Options
| Option | Default | Description |
| ------------- | ------- | --------------------------- |
| Scan Interval | 30 | Update frequency in seconds |
## Entities
### Sensors
| Entity | Description |
| ---------------------------- | ------------------- |
| sensor.{domain}\_temperature | Current temperature |
| sensor.{domain}\_humidity | Current humidity |
### Switches
| Entity | Description |
| ---------------------- | ----------------- |
| switch.{domain}\_power | Main power switch |
## Automation Examples
### Turn on when temperature drops
```yaml
automation:
- alias: 'Low Temperature Alert'
trigger:
- trigger: numeric_state
entity_id: sensor.{domain}_temperature
below: 18
action:
- action: notify.mobile_app
data:
message: 'Temperature dropped below 18°C'
```
## Troubleshooting
### Entity shows "Unavailable"
- Check device is powered on
- Verify network connectivity
- Check integration logs for errors
### Authentication Errors
1. Go to integration settings
2. Click "Configure"
3. Re-enter credentials
## Known Limitations
- Limitation 1
- Limitation 2
## Support
- [GitHub Issues](https://github.com/{username}/{repo}/issues)
- [Home Assistant Community](https://community.home-assistant.io/)
## License
MIT
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.
- 1mo ago First seen · 210 lines · 43 tokens per session scan A 655dfcb01f48
ha-documentation is a skill published in the GitHub repository L3DigitalNet/Claude-Code-Plugins (8 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,285 once invoked, about $0.0002 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.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.