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 larsboes/Axon --skill homectlgit clone --depth 1 https://github.com/larsboes/AxonWrote 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/larsboes/axon/homectl)<a href="https://agentmods.dev/skills/larsboes/axon/homectl"><img src="https://agentmods.dev/badge/skills/larsboes/axon/homectl.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.1 | $0.00059 | $0.00350 |
| Opus 5 | $0.00030 | $0.00175 |
| Sonnet 5 | $0.00012 | $0.00070 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
homectl 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 6d 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.
What it actually says
homectl
Operate the public materialization mechanism over a private Home Assistant definition. Axon owns the parser, validation, and vendoring behavior. The selected overlay owns the templates, variable map, component lockfile, helpers, and generated output.
Commands
scripts/homectl doctor
scripts/homectl materialize
scripts/homectl components [--only NAME] [--dry-run]
Defaults resolve from AXON_OVERLAY_ROOT, AXON_HOME_ROOT, or the overlay declared by
axon.local.toml:
- capability input:
<overlay>/capabilities/home-assistant - variables:
<overlay>/config/home-assistant.vars - generated output:
<overlay>/build/home-assistant - component destination:
<overlay>/config/home-assistant
Every path remains overridable for isolated tests.
Boundary
- Never point generated output into public Axon.
- Never place a real entity ID, hostname, component selection, or device name in this Pack.
- Treat the set of templates and components as a private inventory even when their contents use placeholders and public Git references.
- Review component diffs before replacement; runtime fetching is not allowed.
Read references/templating.md for the token contract and
references/automation-doctrine.md for reusable reliability rules.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 41 lines · 59 tokens per session scan A e4a0f3617b76
homectl is a skill published in the GitHub repository larsboes/Axon (1 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 350 once invoked, about $0.0003 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
usecase-smart-home-brain
Coordinate smart-home actions across existing integrations with clear dry-run and safety confirmation.
ryu-local-model
Search, download, and serve a local GGUF model on a Ryu node via Core's models and engines REST surface. Covers catalog search and device-fit, installing a specific quantization, activating a model, and listing engines (the engine is derived from the model format). Use when a user wants to get a local model running on…
beryl-it-tech
🛠️ Device, system, and network diagnosis.
it-work-reviewer
🔍 Evidence audit for device repair claims.
gx3-existing-project-audit
Analyze an existing Mitsubishi GX Works3 .gx3 project with gx3-cli when the user asks what a ladder does, why a device turns on, or whether a project has risks.
eight-sleep
Unofficial Eight Sleep pod data for AI agents. Writes stay fail-closed. Prefer MCP tools if connected; otherwise the package CLI. Use when the user wants Eight Sleep data or actions through an agent.