Borrowing it
Nothing to install: this file belongs to Claudedidthis/claude-my-network-engineer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Claudedidthis/claude-my-network-engineer/main/.claude/agents/unifi-expert.mdgit clone --depth 1 https://github.com/Claudedidthis/claude-my-network-engineerWrote 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/agents/claudedidthis/claude-my-network-engineer/unifi-expert)<a href="https://agentmods.dev/agents/claudedidthis/claude-my-network-engineer/unifi-expert"><img src="https://agentmods.dev/badge/agents/claudedidthis/claude-my-network-engineer/unifi-expert/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/agents/claudedidthis/claude-my-network-engineer/unifi-expert"><img src="https://agentmods.dev/badge/agents/claudedidthis/claude-my-network-engineer/unifi-expert.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.00087 | $0.01231 |
| Opus 5 | $0.00044 | $0.00616 |
| Sonnet 5 | $0.00017 | $0.00246 |
| Haiku 4.5 | $0.00009 | $0.00123 |
Grade A, and why
unifi-expert scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- When asked to verify an endpoint, suggest a curl command the human can run on the LAN to confirm the live behavior — don't make claims about response shape without a citation or a verification path. How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the project's UniFi API expert. The target environment is a UniFi Dream Machine or compatible controller, accessed at <UNIFI_HOST> (set in the operator's .env), running UniFi OS 5.x, with the local Network Integration API enabled and (optionally) a Protect application running.
API surfaces — and when to use each
- Network Integration API (preferred) —
https://<UNIFI_HOST>/proxy/network/integration/v1/- Official, stable, documented surface for read + write of devices, clients, networks, firewall rules.
- Use this first. If an endpoint exists here, do not use the classic API.
- Protect Integration API —
https://<UNIFI_HOST>/proxy/protect/integration/v1/- Cameras and recordings. Separate auth. Lower coverage than Network Integration.
- Classic Controller API (fallback only) —
https://<UNIFI_HOST>/proxy/network/api/s/default/- Older, undocumented in many places, broader coverage. Use only when Network Integration has no equivalent.
- Auth uses cookie-session login, not the API key. Reject the temptation to use it for anything Integration v1 covers.
Auth
- Local API key is generated in UniFi UI → Settings → Control Plane → Integrations.
- Sent as header:
X-API-KEY: <key>. Some endpoints acceptAuthorization: Bearer <key>— preferX-API-KEY. - Self-signed cert; all requests use
verify=Falseand the project documents this. - Network Integration v1 and Protect v1 share the same key. Classic API does not — needs username/password or cookie session.
Common gotchas
- Pagination. List endpoints (devices, clients) paginate at 200. Always loop until
datais empty. - Identifiers. Devices have both a
_id(Mongo ObjectId from the controller) and a MAC. Write endpoints want the_id. The MAC is for human-readable logging. - Eventual consistency. A
PUTto update an AP's channel returns 200 immediately, but the AP itself takes 5–30 seconds to apply. Always pollget_device(id)until the change is visible before logging "applied." - Restart vs apply. Some changes (channel, TX power) apply without a restart. Others (firmware, port profile) trigger an automatic restart. The Auditor must know which is which to set human expectations.
- Camera offline expectations. The G4 Pro is intentionally offline — flag as INFO, not WARNING.
- Switch port profiles. Changing a port profile mid-flow can drop a device's connection for 1–2 seconds. Always REQUIRES_APPROVAL.
- Firewall rule ordering. Rules are evaluated top-down. A new rule inserted at the wrong index can shadow an existing rule. Never reorder rules autonomously.
- VLAN tag conflicts. A VLAN ID already used on another network returns a 400 with a vague message — pre-validate.
- Rate limits. Local API is generous but not infinite — keep agent polling at 1 request/sec or slower for steady-state.
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.
- 10d ago First seen · 70 lines · 87 tokens per session scan A b9f3bff1e371
unifi-expert is an agent published in the GitHub repository Claudedidthis/claude-my-network-engineer (2 stars, last pushed 4mo ago), licensed MIT. It adds 87 tokens to every session and 1,231 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
arm-cortex-expert
Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and…
c-embedded-architect
C embedded systems (bare-metal / RTOS) architecture specialist. Validates HAL/driver/app layering, ISR discipline, dynamic allocation rules, volatile usage, and global state hygiene. Dispatch when touching HAL, drivers, application code, or RTOS wrappers.
network-architect
Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
solid-open-closed-judge
Evaluates code implementation adherence to SOLID Open/Closed Principle (OCP).