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-troubleshoot-clientgit 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-troubleshoot-client)<a href="https://agentmods.dev/skills/mikeholownych/unifi-mcp/unifi-troubleshoot-client"><img src="https://agentmods.dev/badge/skills/mikeholownych/unifi-mcp/unifi-troubleshoot-client/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-troubleshoot-client"><img src="https://agentmods.dev/badge/skills/mikeholownych/unifi-mcp/unifi-troubleshoot-client.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.00065 | $0.00733 |
| Opus 5 | $0.00032 | $0.00367 |
| Sonnet 5 | $0.00013 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
unifi-troubleshoot-client 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 0 — Version check (always first)
Fetch get_sysinfo and note the Network application version. The controller
facts in this skill were verified on Network 10.x / UniFi OS 5.x; on older
versions expect differences (e.g., legacy stat/alarm exists, band steering
uses an older flag). Adapt claims to the version you see.
UniFi Client Troubleshooting
Systematic diagnosis of a single misbehaving client: connectivity state, RF quality, roaming history, blocking/firewall status, and path to fix.
Context
- Resolve the client:
list_all_clientsmatches name/MAC (includes offline);list_clientsfor currently connected only. Tryget_client_detailswith MAC once found. If given an IP only, match it against both lists. - Auth note: in Integration API mode client details are degraded; prefer local.
Workflow
- Presence & identity — is it known? online? wired or wireless? which AP/switch?
- Block check —
blockedflag on details; also scanget_firewall_policiesfor BLOCK rules whose source zone contains the client. - RF quality (wireless): signal/RSSI, noise, tx/rx rate, satisfaction,
channel + band vs the AP's radio table (
list_devices).- signal < -70 dBm → coverage problem
- low tx_rate despite good signal → interference or legacy protocol
- roam_count high → steering/flapping issue
- IP layer — has an IP? correct VLAN/network? DHCP reservation conflicts
(
use_fixedipvs current IP mismatch)? - History & events —
troubleshoot_clientdeep-dive;get_recent_eventsmay be empty on Network 10+ (endpoints removed) — say so once if so. - Compare peers — other clients on same AP/band via
list_clients: if all bad → AP problem; only this one → client problem. - Verdict + fix plan, e.g.:
- Blocked → confirm with user →
unblock_client - Weak signal → suggest AP placement/channel plan (defer to unifi-wifi-optimize)
- IP conflict → propose reservation update
- Flapping → check min-RSSI/bss_transition settings
- Blocked → confirm with user →
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 · 67 lines · 0 tokens per session scan A 9d31824524cb
unifi-troubleshoot-client is a skill published in the GitHub repository mikeholownych/unifi-mcp (0 stars, last pushed 12d ago), licensed MIT. It adds 65 tokens to every session and 733 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
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…