ops:home-agent

ops:home-agent is an agent for Claude Code from Lifecycle-Innovations-Limited/claude-ops. It costs 13 tokens per session (1,254 once invoked), scanned A, original, MIT.

A read-only operations agent for checking a Homey Pro smart-home hub. Homey Pro is a device that connects and automates household equipment such as lights, sensors, alarms, and appliances.

In plain words
What is it for?
Use it to inspect connected devices, automations called flows, energy data, presence, alarms, and household zones.
Why use it?
It collects information from the hub without changing devices or automations, using the local connection first and a cloud connection if needed.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter; positional $N argument.

Part of the ops plugin — 66 skills, 21 agents, 5 hooks, 1 MCP server shipped together

Good fit Use it to inspect connected devices, automations called flows, energy data, presence, alarms, and household zones.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/lifecycle-innovations-limited/claude-ops/ops-home-agent
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-ops

Made for: Claude Code.

Or install ops, the plugin that ships this one along with the rest of its 66 skills, 21 agents, 5 hooks, 1 MCP server.

Wrote 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.

agentmods badge for ops:home-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/ops-home-agent/github.svg)](https://agentmods.dev/agents/lifecycle-innovations-limited/claude-ops/ops-home-agent)
Your own site
<a href="https://agentmods.dev/agents/lifecycle-innovations-limited/claude-ops/ops-home-agent"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/ops-home-agent/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.

agentmods 80×15 button for ops:home-agent

Your own site · 80×15
<a href="https://agentmods.dev/agents/lifecycle-innovations-limited/claude-ops/ops-home-agent"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/ops-home-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,254 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.01254
Opus 5 $0.00006 $0.00627
Sonnet 5 $0.00003 $0.00251
Haiku 4.5 $0.00001 $0.00125

Measured 9d ago against content hash eb1fb8a35292, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ops:home-agent scanned grade A with 1 finding 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 9d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

http_code=$(curl -s -o /tmp/homey_resp -w "%{http_code}" \
claude-ops/agents/ops:home-agent.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OPS:HOME AGENT — Homey Pro probe

Read-only probe for a Homey Pro hub. Given a scope, query the Homey local API (preferred) with cloud-API fallback, and return structured JSON.

Input

The calling skill provides:

  • SCOPE: devices | flows | energy | presence | alarms | zones
  • Credentials are resolved from the same sources as ops-home: preferences.json → env vars → Doppler (homey-pro) → keychain.

Phase 1 — Resolve credentials

PREFS_PATH="${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json"
_save_HOMEY_LOCAL_URL="${HOMEY_LOCAL_URL-}"
_save_HOMEY_LOCAL_TOKEN="${HOMEY_LOCAL_TOKEN-}"
_save_HOMEY_CLOUD_TOKEN="${HOMEY_CLOUD_TOKEN-}"
_save_HOMEY_ID="${HOMEY_ID-}"
HOMEY_LOCAL_URL=$(jq -r '.home_automation.homey_local_url // empty' "$PREFS_PATH" 2>/dev/null)
HOMEY_LOCAL_TOKEN=$(jq -r '.home_automation.homey_local_token // empty' "$PREFS_PATH" 2>/dev/null)
HOMEY_CLOUD_TOKEN=$(jq -r '.home_automation.homey_cloud_token // empty' "$PREFS_PATH" 2>/dev/null)
HOMEY_ID=$(jq -r '.home_automation.homey_id // empty' "$PREFS_PATH" 2>/dev/null)

[ -z "$HOMEY_LOCAL_URL" ] && HOMEY_LOCAL_URL="${_save_HOMEY_LOCAL_URL:-}"
[ -z "$HOMEY_LOCAL_TOKEN" ] && HOMEY_LOCAL_TOKEN="${_save_HOMEY_LOCAL_TOKEN:-}"
[ -z "$HOMEY_CLOUD_TOKEN" ] && HOMEY_CLOUD_TOKEN="${_save_HOMEY_CLOUD_TOKEN:-${HOMEY_ACCESS_TOKEN:-}}"
[ -z "$HOMEY_ID" ] && HOMEY_ID="${_save_HOMEY_ID:-}"

If neither local nor cloud credentials resolve, return:

{ "scope": "<scope>", "error": "no credentials", "fallback_attempted": false }

Phase 2 — Probe (try local, fall back to cloud)

probe() {
  local local_path="$1" cloud_path="$2"
  local resp http_code
  if [ -n "$HOMEY_LOCAL_URL" ] && [ -n "$HOMEY_LOCAL_TOKEN" ]; then
    http_code=$(curl -s -o /tmp/homey_resp -w "%{http_code}" \
      -H "Authorization: Bearer ${HOMEY_LOCAL_TOKEN}" \
      "${HOMEY_LOCAL_URL}/api/manager${local_path}" --max-time 5 2>/dev/null)
    if [ "$http_code" -ge 200 ] && [ "$http_code" -lt 300 ]; then
      cat /tmp/homey_resp
      echo "TRANSPORT=local" >&2
      return 0
    fi
  fi
  if [ -n "$HOMEY_CLOUD_TOKEN" ] && [ -n "$HOMEY_ID" ]; then
    curl -s -H "Authorization: Bearer ${HOMEY_CLOUD_TOKEN}" \
      "https://api.athom.com/v2/homey/${HOMEY_ID}${cloud_path}" --max-time 10
    echo "TRANSPORT=cloud" >&2
    return 0
  fi
  echo '{"error":"no transport"}'
  return 1
}

Read the full file on GitHub · 126 lines

Changes

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.

  1. 9d ago First seen · 126 lines · 13 tokens per session scan A eb1fb8a35292

Subscribe to this mod's changes

ops:home-agent is an agent published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (187 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 1,254 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

ha-pattern-analyst

Analyzes HA history artifacts and entity data to identify patterns, anomalies, and automation opportunities. Cheap and fast — read-only.

gtapps/claude-code-hermit · 31 tokens

kpz

ML engineering specialist sub-agent. Designs and implements inference pipelines, provider selection, quantization strategies, and hardware abstraction for ONNX models. Benchmark-driven — measures before optimizing.

punt-labs/vox · 37 tokens

amnesia-verifier

Context-free PCB design verifier ("amnesia audit"). Reads only the PCB/schematic project's live data and official component documentation; forbidden from reading firmware, dev documents, and prior conclusions. Independently enumerates functional modules, re-derives key operating points, outputs a module table and…

raisoninme/boardless-pcb · 118 tokens

c-embedded-architect

C embedded systems (bare-metal / RTOS) architecture specialist. Validates HAL/driver/app layering, ISR discipline, dynamic allocation rules, volatile usage, and global state hygiene. Dispatch when touching HAL, drivers, application code, or RTOS wrappers.

onlygian/G-Forge · 57 tokens

hardware-as-code-engineer

Computational-engineering specialist for simulation-in-the-loop, hardware-as-code projects (parametric CAD + scored audits + sims). Invoke when designing, building, auditing, or iterating a hardware model where geometry is code, a design.json is the source of truth, and every requirement must earn an executable…

JMMonte/agentic-digital-twin · 100 tokens

qec-hardware-engineer

QECTOR hardware/quantum-architecture engineer. Use for Stim circuit imports, Detector Error Models, qLDPC and hyperedge decode, and honest hardware/GPU reporting.

GuillaumeLessard/qector-claude-plugin · 42 tokens