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 mikeholownych/unifi-mcp --skill unifi-internet-downgit clone --depth 1 https://github.com/mikeholownych/unifi-mcpWrote 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/mikeholownych/unifi-mcp/unifi-internet-down)<a href="https://agentmods.dev/skills/mikeholownych/unifi-mcp/unifi-internet-down"><img src="https://agentmods.dev/badge/skills/mikeholownych/unifi-mcp/unifi-internet-down/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/mikeholownych/unifi-mcp/unifi-internet-down"><img src="https://agentmods.dev/badge/skills/mikeholownych/unifi-mcp/unifi-internet-down.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.00035 | $0.00681 |
| Opus 5 | $0.00017 | $0.00341 |
| Sonnet 5 | $0.00007 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
unifi-internet-down 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 12d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UniFi Internet Down Triage
Calm, plain-English diagnosis when someone loses internet. No jargon without translation. Find the broken link before recommending anyone call their ISP.
Golden rule
Work from the wall outward: provider line → router → home network → the device. Each step either finds the problem or rules it out.
Workflow
- Scope it — if the user hasn't said: "Is it everything in the house, or one device?" Everything → steps 2–4. One device → step 5.
- Check the provider line (WAN) —
get_site_health/get_network_health:- WAN status
okwith a public IP → line is fine, skip to 4/5. - WAN down/no IP → the problem is the modem or provider. Go to step 3.
- WAN status
- Modem/provider playbook — say this plainly:
- Unplug the modem's power for 30 seconds, plug back in, wait 2 minutes.
- Still down after also restarting the gateway? Note the exact status you observed and give the user a short script for calling their ISP ("my line is down at the router; the modem shows no signal" + account info).
- Only restart network gear with explicit approval; warn it drops all connections for ~2 minutes.
- Whole-house check with line up — rare; look for:
- Devices restarting (
list_devices, uptime minutes = recent crash) - Speed collapse → offer
run_speed_test(tell them it pauses internet ~1 min)
- Devices restarting (
- Single device — pivot: is the rest of the house fine?
- Device not on the network at all →
unifi-setup-new-devicestyle checks (wrong password, smart gadget needing 2.4GHz, airplane mode). - Connected but no internet → try
unblock_clientcheck first (blocked devices silently fail), then reboot guidance for that device.
- Device not on the network at all →
Translation table (use these phrasings)
| Technical | Say |
|---|---|
| WAN down | "The line from your provider is down" |
| DHCP | "Getting an address on the network" |
| Latency high | "Slow responses, likely congestion" |
| Client blocked | "This device was blocked from the network (someone may have paused it)" |
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.
- 12d ago First seen · 65 lines · 35 tokens per session scan A ab9021bbca78
unifi-internet-down is a skill published in the GitHub repository mikeholownych/unifi-mcp (0 stars, last pushed 12d ago), licensed MIT. It adds 35 tokens to every session and 681 once invoked, about $0.0002 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
gke-ai-troubleshooting-tpu-dynamic-slices-monitoring
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
competition-firmware-layout
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for firmware images, partition tables, boot chains, update packages, extracted filesystems, embedded configs, and device-facing trust boundaries. Use when the user asks to unpack firmware, map partition layout, inspect bootloader or init…
doca-flow
Build and debug DOCA Flow applications on supported NVIDIA NICs/DPUs: define match/action pipes, initialize ports and representors, choose forwarding targets, validate pipes before hardware programming, read counters, match the Flow version to the installed DOCA release, and diagnose Flow API errors. Trigger on DOCA…
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
catc-troubleshoot
Catalyst Center troubleshooting workflows - device unreachable investigation, client connectivity issues, interface down analysis, site-wide outage triage, wireless roaming problems, integration with pyATS for CLI-level diagnostics. Use when a device is unreachable, a user reports connectivity problems, an interface…