unifly-status

unifly-status is a command for Claude Code from hyperb1iss/unifly. It costs 22 tokens per session (411 once invoked), scanned A, original, Apache-2.0.

A quick health-check command for UniFi, Ubiquiti’s network-management system. It checks the controller, device states, active alarms, and connected clients.

In plain words
What is it for?
Use it for a routine UniFi status report. It summarizes controller availability, device counts by state, active alarms, and client count.
Why use it?
It gives a compact view of whether the network is healthy and highlights offline devices or unresolved alarms.

Command for Claude Code

Written for Claude Code: arguments in frontmatter.

Part of the unifly plugin — 1 skill, 2 commands, 1 agent shipped together

Good fit Use it for a routine UniFi status report. It summarizes controller availability, device counts by state, active alarms, and client count.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hyperb1iss/unifly/unifly-status
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/hyperb1iss/unifly

Made for: Claude Code.

Or install unifly, the plugin that ships this one along with the rest of its 1 skill, 2 commands, 1 agent.

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 unifly-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/hyperb1iss/unifly/unifly-status.svg)](https://agentmods.dev/commands/hyperb1iss/unifly/unifly-status)
Your own site
<a href="https://agentmods.dev/commands/hyperb1iss/unifly/unifly-status"><img src="https://agentmods.dev/badge/commands/hyperb1iss/unifly/unifly-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 411 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00022 $0.00411
Opus 5 $0.00011 $0.00205
Sonnet 5 $0.00004 $0.00082
Haiku 4.5 $0.00002 $0.00041

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

Security

Grade A, and why

unifly-status 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 7d 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.

commands/unifly-status.md · 59 lines

What it actually says

UniFi Status Check

Run a comprehensive health check of the UniFi infrastructure.

Execution

  1. Verify controller connectivity via unifly system health
  2. Count online vs offline devices via unifly devices list --all -o json
  3. Check for active alarms via unifly alarms list --unarchived -o json
  4. Report findings in a clear summary

Basic Status

unifly system health -p {{profile}} -o json

Full Status Report

# Controller health
unifly system health -p {{profile}} -o json

# Device summary
unifly devices list --all -p {{profile}} -o json | jq '{
  total: length,
  online: [.[] | select(.state == "ONLINE")] | length,
  offline: [.[] | select(.state == "OFFLINE")] | length,
  pending: [.[] | select(.state == "PENDING")] | length
}'

# Active alarms
unifly alarms list --unarchived -p {{profile}} -o json | jq 'length'

# Client count
unifly clients list --all -p {{profile}} -o json | jq 'length'

When -p {{profile}} is provided, the -p {{profile}} flag is already wired into every command above; no further substitution is needed.

Result Reporting

Summarize the health check:

  • Controller status (healthy/degraded/unreachable)
  • Device counts by state
  • Number of active alarms (highlight if > 0)
  • Connected client count
  • Any offline devices (list names and MACs)
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. 7d ago First seen · 59 lines · 22 tokens per session scan A 895defdead44

Subscribe to this mod's changes

unifly-status is a command published in the GitHub repository hyperb1iss/unifly (251 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 411 once invoked, about $0.0001 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-30.