unifi-whos-home

unifi-whos-home is a skill for Claude Code from mikeholownych/unifi-mcp. It costs 0 tokens per session (746 once invoked), scanned A, original, MIT.

A guide for diagnosing one misbehaving device on a UniFi network, whether it uses WiFi or a cable. It checks the device's connection, signal quality, roaming history, blocking status, and route through the network.

In plain words
What is it for?
Use it when a device is slow, disconnects, cannot connect, cannot reach the internet, or has roaming problems.
Why use it?
It replaces guesswork with checks that distinguish a weak wireless signal, blocked access, roaming trouble, or another network problem. A client means any connected device, such as a phone, laptop, or camera.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it when a device is slow, disconnects, cannot connect, cannot reach the internet, or has roaming problems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mikeholownych/unifi-mcp/unifi-whos-home
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.

Any agent
npx skills add mikeholownych/unifi-mcp --skill unifi-whos-home
Clone the repo
git clone --depth 1 https://github.com/mikeholownych/unifi-mcp

Made for: Claude Code.

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 unifi-whos-home

README.md
[![agentmods](https://agentmods.dev/badge/skills/mikeholownych/unifi-mcp/unifi-whos-home/github.svg)](https://agentmods.dev/skills/mikeholownych/unifi-mcp/unifi-whos-home)
Your own site
<a href="https://agentmods.dev/skills/mikeholownych/unifi-mcp/unifi-whos-home"><img src="https://agentmods.dev/badge/skills/mikeholownych/unifi-mcp/unifi-whos-home/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.

agentmods 80×15 button for unifi-whos-home

Your own site · 80×15
<a href="https://agentmods.dev/skills/mikeholownych/unifi-mcp/unifi-whos-home"><img src="https://agentmods.dev/badge/skills/mikeholownych/unifi-mcp/unifi-whos-home.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 746 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.00000 $0.00746
Opus 5.5 $0.00000 $0.00298
Sonnet 5.5 $0.00000 $0.00149
Haiku 4.5 $0.00000 $0.00075

Measured 2mo ago against content hash cb9c7f7b5882, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

unifi-whos-home 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 2mo 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.

skills/unifi-whos-home/SKILL.md · 65 lines

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 Who's Home

Friendly inventory of everything connected to the network, translated into everyday language — plus careful handling of genuinely unknown devices.

Key knowledge

  • Randomized MACs are normal: modern phones/laptops use a different fake MAC per WiFi network and often lack hostnames. A phone can appear as "Unknown (Apple)" — that is not an intruder.
  • OUI tells you the maker: the start of a MAC identifies the manufacturer (the client oui field). Translate: Apple→iPhone/Mac, Samsung→TV/phone, Sonos→speaker, Raspberry-Pi/Proxmox→homelab box, etc.
  • Infra devices must never be blocked: APs, switches, NAS, DNS servers. Cross-check candidates against list_devices (your actual hardware) before proposing any block.

Workflow

  1. Inventory — list_clients (connected now); group as:
    • Your equipment (matches list_devices)
    • Recognizable family stuff (named or obvious OUI: phones, TVs, printers)
    • Unknown — list separately with every clue: maker (oui), name/hostname, connection type, first/last seen.
  2. Translate each unknown: "Unknown 'bc:24:11…' = a virtual machine on your Proxmox server", "Unknown 'Apple' = someone's iPhone using private-address mode".
  3. Suspicion checklist (only flag if several hold):
    • wireless + unknown maker + active right now + nobody recognizes it
    • appeared between dates the user can place
    • NOT seen on wired ports
  4. For each unknown, ask the owner-in-the-house: "do you own a [maker] device?"
    • Yes → suggest naming it in the UniFi app so future audits are clean.
    • No / unsure → offer block_client AFTER stating plainly what blocking does ("it will be kicked off and unable to rejoin until we allow it back") and get explicit confirmation.
  5. Reassure with facts: WPA2/WPA3 means strangers can't join without the password; unknown entries are usually family gadgets with privacy features.

Output format

Who's home right now: [N devices]
🏠 Your gear: [count] · 👪 Recognized: [count] · ❓ Unknown: [count]

❓ Unknown devices:
1. [maker/OS guess] — [name] — [where seen] — [first seen date]
   Likely is: [best plain-English guess]

Want me to [action] on #X?

Read the full file on GitHub · 65 lines

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. 2mo ago First seen · 65 lines · 0 tokens per session scan A cb9c7f7b5882

Subscribe to this mod's changes

unifi-whos-home is a skill published in the GitHub repository mikeholownych/unifi-mcp (2 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 746 tokens. 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.

Related

unifi-whos-home compared with skills from other repositories

unifi-whos-home next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
unifi-whos-homemikeholownych/unifi-mcpSkill213d agoMITA0Claude Code
gke-compute-classesgoogle/skillsSkill22kyesterdayApache-2.0A83Claude Code, Codex
jetson-diagnosticNVIDIA/skillsSkill3.9kyesterdayApache-2.0A30Claude Code, Codex
holoscan-install-wheelNVIDIA/skillsSkill3.9kyesterdayApache-2.0A34Claude Code, Codex
offensive-z-waveSnailSploit/Claude-RedSkill10k25d agoMITA113Claude Code, Codex
doca-socket-relayNVIDIA/skillsSkill3.9kyesterdayApache-2.0A236Claude Code, Codex
hsb-flashNVIDIA/skillsSkill3.9kyesterdayApache-2.0B94Claude Code