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 t3chnaztea/unifi-skills --skill unifi-context-mapgit clone --depth 1 https://github.com/t3chnaztea/unifi-skillsWrote 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/t3chnaztea/unifi-skills/unifi-context-map)<a href="https://agentmods.dev/skills/t3chnaztea/unifi-skills/unifi-context-map"><img src="https://agentmods.dev/badge/skills/t3chnaztea/unifi-skills/unifi-context-map/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/t3chnaztea/unifi-skills/unifi-context-map"><img src="https://agentmods.dev/badge/skills/t3chnaztea/unifi-skills/unifi-context-map.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00155 | $0.02238 |
| Opus 5 | $0.00077 | $0.01119 |
| Sonnet 5 | $0.00031 | $0.00448 |
| Haiku 4.5 | $0.00015 | $0.00224 |
Grade A, and why
unifi-context-map 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UniFi Context Map
This repo deliberately ships no network inventory, because the useful one is yours. This skill is how the agent builds it.
An agent working a UniFi network without a map guesses: which AP is the one in
the back bedroom, whether 10.x.x.50 is the NAS or a decommissioned print
server, whether that camera reservation reflects where the camera actually is.
UniFi answers with MAC addresses and machine names, and it is confidently wrong
in a specific way: the config is not the operational reality. A reservation
exists whether or not the device honors it. A port override is stored whether or
not the hardware enforces it.
One markdown file, one human pass, fixes this.
Read this before you write anything down
A complete UniFi map is a burglary aid. Not being dramatic: assembled in one file it contains camera names and their physical placements, which cameras are on which segment, your WAN address, the MAC address of every device in the building, your alarm panel's IP, and which SSID is the trusted one. That is a casing document with a network diagram attached.
So, before the first line:
- Never commit it to a public repo. Not "scrub it later". Git history is forever and the scrub is always harder than you think.
.gitignoreit by name in whatever repo you do network work from. A suggested pattern is in this repo's.gitignore.- Never paste it into a shared or third-party context you do not control.
- The API key never goes in it. Env var, always, same as
unifi-connect. - If you do keep it in a repo, keep that repo private, and assume any file an agent reads freely is a file that can end up somewhere you did not intend.
This warning exists because the private skill this repo was distilled from could not be published as-written. Roughly seventy percent of it was exactly the inventory described above.
Where to keep it
Wherever your agent reads context from and nowhere else: the private repo you do network work from, or a local notes directory. Keep it in one place so there is one thing to protect.
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 · 225 lines · 155 tokens per session scan A dec18e22fb60
unifi-context-map is a skill published in the GitHub repository t3chnaztea/unifi-skills (39 stars, last pushed 20d ago), licensed MIT. It adds 155 tokens to every session and 2,238 once invoked, about $0.0008 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.
Other skills, from other repositories
unifi-cli
Use when asked about UniFi network gear or the local network — access points, gateway, switches, WiFi, or which clients/devices are connected. Queries the local UniFi gateway via the unifi CLI.
lab-hardware-cad
Design custom laboratory hardware as parametric build123d models and export fabrication-ready STEP, STL, and DXF files - microfluidic chips and molds, optomechanical mounts and breadboard adapters, cuvette and microplate holders, tube racks, animal-behavior rigs, and 3D-printed instrument fixtures. Use when a research…
opentrons-integration
Author, review, migrate, simulate, and troubleshoot official Opentrons Python Protocol API v2 protocols for Flex and OT-2 robots. Use for robot-specific liquid handling, deck and labware setup, pipettes, modules, runtime parameters, liquid classes, and Opentrons App analysis. Use pylabrobot instead when one workflow…
pylabrobot
Develop and review PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Use for PyLabRobot protocols or API questions; keep physical execution behind an explicit operator safety gate.
offensive-wifi
Wireless / 802.11 attack methodology for red team engagements and wireless security assessments. Covers monitor-mode setup, WPA/WPA2-PSK handshake capture and PMKID attacks, WPA3 SAE downgrade and Dragonblood, WPA-Enterprise (EAP) attacks (MSCHAPv2 cracking, EAP-TLS cert theft, evil-twin RADIUS), Karma / Known Beacons…
offensive-wifi-recon
Wi-Fi reconnaissance methodology — adapter selection, monitor mode and packet injection setup, regulatory domain handling, multi-band airspace mapping, hidden SSID discovery, BSSID/ESSID/channel/PMF/encryption fingerprinting, client probe analysis, vendor OUI lookup, war-driving with Kismet/airodump-ng/Wigle, and…