Borrowing it
Nothing to install: this file belongs to sirkirby/unifi-mcp. 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/sirkirby/unifi-mcp/main/.agents/skills/add-integration-api-tool/SKILL.mdgit clone --depth 1 https://github.com/sirkirby/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/sirkirby/unifi-mcp/add-integration-api-tool)<a href="https://agentmods.dev/skills/sirkirby/unifi-mcp/add-integration-api-tool"><img src="https://agentmods.dev/badge/skills/sirkirby/unifi-mcp/add-integration-api-tool/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/sirkirby/unifi-mcp/add-integration-api-tool"><img src="https://agentmods.dev/badge/skills/sirkirby/unifi-mcp/add-integration-api-tool.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.00141 | $0.01972 |
| Opus 5 | $0.00071 | $0.00986 |
| Sonnet 5 | $0.00028 | $0.00394 |
| Haiku 4.5 | $0.00014 | $0.00197 |
Grade A, and why
add-integration-api-tool 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 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.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- add-integration-api-tool — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding a Tool That Uses the UniFi Integration API
The UniFi controller exposes two API surfaces. They are not interchangeable. Skipping this distinction creates silent footguns where IDs from one API are accepted by tools backed by the other and silently fail — or worse, succeed against the wrong resource.
The two surfaces
| V2 controller API | Integration API | |
|---|---|---|
| Auth | session cookie | X-API-Key header |
| Path prefix | /proxy/network/api/..., /proxy/network/v2/api/... |
/proxy/network/integration/v1/... |
| IDs | Mongo ObjectIDs (674f0...) |
UUIDs (0998be5a-...) |
| Field naming | snake_case |
camelCase |
| Action shape | "action": "ALLOW" + flat fields |
nested {"action": {"type": "ALLOW", "allowReturnTraffic": true}} |
ip_version |
"BOTH" |
"ipProtocolScope": {"ipVersion": "IPV4_AND_IPV6"} |
| Coverage | everything the web UI uses | curated, expanding subset |
| Membership | full controller state | filtered (system policies often excluded) |
These differences are not cosmetic. The same logical resource appears in V2 with a Mongo ID and in Integration with a UUID, with no native bridge field connecting them.
Step 1: Identify the family
A tool family is a set of tools whose returned IDs and accepted IDs are interchangeable.
- Reading + writing to the same API endpoint group? Same family.
- Reading from V2 and writing to V2? Same family (the existing firewall policy CRUD family).
- Reading from Integration and writing to Integration? Same family.
- Mixing? You're inventing a bridging tool — see Step 5.
Current families in this codebase:
| Family | API | IDs | Tools |
|---|---|---|---|
| Firewall policy CRUD | V2 | Mongo | unifi_list_firewall_policies, unifi_get_firewall_policy_details, create / update / delete / toggle |
| Firewall policy ordering | Integration | UUID | unifi_get_firewall_policy_ordering + unifi_reorder_firewall_policies |
If your new tool fits cleanly inside an existing family, join it. If not, start a new family — and document its boundary.
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 · 206 lines · 141 tokens per session scan A b2d119edc742
add-integration-api-tool is a skill published in the GitHub repository sirkirby/unifi-mcp (797 stars, last pushed yesterday), licensed MIT. It adds 141 tokens to every session and 1,972 once invoked, about $0.0007 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
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this…
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
frontmcp-development
Use when building any FrontMCP server component other than a tool (for tools, use create-tool). Covers @Resource static resources and parameterized URI templates; @Prompt reusable prompts (RAG, multi-turn); @Provider singleton dependency-injection providers (database pools, API clients); @Agent autonomous LLM agents…
pipefy-api-fallback
Use this skill when an MCP tool fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow the 3-tier…