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.
git clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-opsWrote 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/agents/lifecycle-innovations-limited/claude-ops/ops-unifi-agent)<a href="https://agentmods.dev/agents/lifecycle-innovations-limited/claude-ops/ops-unifi-agent"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/ops-unifi-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.
<a href="https://agentmods.dev/agents/lifecycle-innovations-limited/claude-ops/ops-unifi-agent"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/ops-unifi-agent.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.00013 | $0.01596 |
| Opus 5 | $0.00006 | $0.00798 |
| Sonnet 5 | $0.00003 | $0.00319 |
| Haiku 4.5 | $0.00001 | $0.00160 |
Grade A, and why
ops:unifi-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 10d 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.
sm_call() { curl -s --max-time 15 -H "X-API-Key: ${UNIFI_SM_KEY}" -H "Accept: application/json" "https://api.ui.com$1"; } How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPS:UNIFI AGENT — UniFi probe
Read-only probe for UniFi infrastructure. Given a surface scope, query the relevant UniFi API and return structured JSON. Three surfaces:
- site-manager — cloud,
https://api.ui.com, fleet-wide hosts/sites/devices/ISP metrics. - network — local,
${UNIFI_LOCAL_URL}/proxy/network/integration/v1, per-console devices + clients. - protect — local,
${UNIFI_PROTECT_URL}/proxy/protect/integration/v1, cameras + NVR.
Input
The calling skill provides:
SCOPE:site-manager|network|protect- Optional
SITE_ID(for network/protect drill-downs). - Credentials resolved from the same sources as
ops-unifi:preferences.json(home_network.*) → env vars → Doppler (unifi) → keychain.
Phase 1 — Resolve credentials
PREFS_PATH="${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json"
UNIFI_SM_KEY=$(jq -r '.home_network.unifi_site_manager_api_key // empty' "$PREFS_PATH" 2>/dev/null)
UNIFI_LOCAL_URL=$(jq -r '.home_network.unifi_local_gateway_url // empty' "$PREFS_PATH" 2>/dev/null)
UNIFI_LOCAL_KEY=$(jq -r '.home_network.unifi_local_api_key // empty' "$PREFS_PATH" 2>/dev/null)
UNIFI_PROTECT_URL=$(jq -r '.home_network.unifi_protect_url // empty' "$PREFS_PATH" 2>/dev/null)
UNIFI_PROTECT_KEY=$(jq -r '.home_network.unifi_protect_api_key // empty' "$PREFS_PATH" 2>/dev/null)
[ -z "$UNIFI_SM_KEY" ] && UNIFI_SM_KEY="${UNIFI_SITE_MANAGER_API_KEY:-}"
[ -z "$UNIFI_LOCAL_URL" ] && UNIFI_LOCAL_URL="${UNIFI_LOCAL_GATEWAY_URL:-}"
[ -z "$UNIFI_LOCAL_KEY" ] && UNIFI_LOCAL_KEY="${UNIFI_LOCAL_API_KEY:-}"
[ -z "$UNIFI_PROTECT_URL" ] && UNIFI_PROTECT_URL="${UNIFI_PROTECT_URL:-$UNIFI_LOCAL_URL}"
[ -z "$UNIFI_PROTECT_KEY" ] && UNIFI_PROTECT_KEY="${UNIFI_PROTECT_API_KEY:-$UNIFI_LOCAL_KEY}"
# Doppler fallback (project: unifi)
if command -v doppler &>/dev/null; then
[ -z "$UNIFI_SM_KEY" ] && UNIFI_SM_KEY=$(doppler secrets get UNIFI_SITE_MANAGER_API_KEY --project unifi --plain 2>/dev/null)
[ -z "$UNIFI_LOCAL_URL" ] && UNIFI_LOCAL_URL=$(doppler secrets get UNIFI_LOCAL_GATEWAY_URL --project unifi --plain 2>/dev/null)
[ -z "$UNIFI_LOCAL_KEY" ] && UNIFI_LOCAL_KEY=$(doppler secrets get UNIFI_LOCAL_API_KEY --project unifi --plain 2>/dev/null)
[ -z "$UNIFI_PROTECT_KEY" ] && UNIFI_PROTECT_KEY=$(doppler secrets get UNIFI_PROTECT_API_KEY --project unifi --plain 2>/dev/null)
fi
# Keychain fallback (macOS)
[ -z "$UNIFI_SM_KEY" ] && UNIFI_SM_KEY=$(security find-generic-password -s "unifi-site-manager-key" -w 2>/dev/null)
[ -z "$UNIFI_LOCAL_KEY" ] && UNIFI_LOCAL_KEY=$(security find-generic-password -s "unifi-local-key" -w 2>/dev/null)
[ -z "$UNIFI_PROTECT_KEY" ] && UNIFI_PROTECT_KEY=$(security find-generic-password -s "unifi-protect-key" -w 2>/dev/null)
[ -z "$UNIFI_PROTECT_URL" ] && UNIFI_PROTECT_URL="$UNIFI_LOCAL_URL"
[ -z "$UNIFI_PROTECT_KEY" ] && UNIFI_PROTECT_KEY="$UNIFI_LOCAL_KEY"
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.
- 10d ago First seen · 122 lines · 13 tokens per session scan A 8c07c896e29f
ops:unifi-agent is an agent published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (187 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 1,596 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.
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.
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.
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…
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.
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…
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.