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-wifi-optimizegit 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-wifi-optimize)<a href="https://agentmods.dev/skills/mikeholownych/unifi-mcp/unifi-wifi-optimize"><img src="https://agentmods.dev/badge/skills/mikeholownych/unifi-mcp/unifi-wifi-optimize/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-wifi-optimize"><img src="https://agentmods.dev/badge/skills/mikeholownych/unifi-mcp/unifi-wifi-optimize.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.00069 | $0.00929 |
| Opus 5 | $0.00034 | $0.00464 |
| Sonnet 5 | $0.00014 | $0.00186 |
| Haiku 4.5 | $0.00007 | $0.00093 |
Grade A, and why
unifi-wifi-optimize 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 — 74 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 WiFi Optimization
Diagnose and fix wireless performance issues on a UniFi site: channel conflicts, suboptimal widths, security mode upgrades, and steering. Every change is shown to the user for approval before it is applied.
Context (read first)
- Require
UNIFI_MODE=local; if tools error with Integration API messages, stop and explain how to switch (local admin required — SSO+MFA won't work). - Gather baseline:
get_wlans,list_devices(AP radio tables),get_client_experience_report,list_clients.
Known controller facts (learned the hard way)
- Band steering: Network 9/10 replaced the old flag with
bss_transition(802.11k/v) on the WLAN. There is no separate band_steering knob. - WPA3 transition =
wpa3_support:true+wpa3_transition:true+pmf_mode:"optional". Keepwpa_mode:"wpa2"so legacy IoT still connects. Pure WPA3 (pmf_mode:"required") breaks older devices. - Channel plan: 2.4GHz must be non-overlapping (1/6/11); with >3 APs one shared pair is acceptable — pick the two physically farthest apart.
- 5GHz width: use 80MHz unless DFS/radar issues are documented; 40MHz halves throughput. 160MHz only for AX-class dense deployments.
- Config pushes to APs briefly interrupt clients (state 5 = provisioning).
Workflow
- Baseline report — per-AP: radio, channel, width; per-WLAN: security, transition flags; client satisfaction distribution. Present findings.
- Build a change plan, each item as: what → from → to → why → impact:
- Channel conflicts → staggered 1/6/11 plan
- Width < 80MHz on 5GHz → 80MHz
- Security < WPA2 → WPA2 minimum; offer WPA3 transition (warn about IoT)
bss_transition:false→ true
- Approval gate — show the full plan; apply only items the user approves.
- Apply via
update_wlanfor SSID-level fields (by SSID name works); device radio changes are not exposed by MCP tools — if needed, say so and point to Settings > WiFi in the UI rather than improvising raw API calls unless the user explicitly requests it. - Verify — re-read
get_wlans; confirm values stuck. Note APs may take ~30s to finish provisioning. - Follow-up check — after changes settle, compare client satisfaction.
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 · 74 lines · 0 tokens per session scan A bd98dffe8f91
unifi-wifi-optimize is a skill published in the GitHub repository mikeholownych/unifi-mcp (0 stars, last pushed 13d ago), licensed MIT. It adds 69 tokens to every session and 929 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-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.