unifi-mcp-server: Skill for Claude Code

.agents/skills/source-command-unifi-mcp-update-docs/SKILL.md

source-command-unifi-mcp-update-docs is a skill for Claude Code, Codex from enuno/unifi-mcp-server. It costs 22 tokens per session (824 once invoked), scanned A, original, Apache-2.0.

A command that builds API.md from the UniFi MCP Server's code. It reads tool and resource descriptions, parameters, return values, errors, and examples from source files.

In plain words
What is it for?
Use it to scan tools and resources, organize them by UniFi feature, preserve existing documentation sections, and generate an updated API reference.
Why use it?
It keeps the API reference aligned with the implemented tools and resources instead of requiring separate manual edits.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is enuno/unifi-mcp-server's own configuration. It tells Claude Code and Codex how to work on unifi-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything unifi-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to enuno/unifi-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/enuno/unifi-mcp-server/main/.agents/skills/source-command-unifi-mcp-update-docs/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/enuno/unifi-mcp-server

Made for: Claude Code, Codex.

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 source-command-unifi-mcp-update-docs

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/enuno/unifi-mcp-server/source-command-unifi-mcp-update-docs"><img src="https://agentmods.dev/badge/skills/enuno/unifi-mcp-server/source-command-unifi-mcp-update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 824 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Agent Snooping · line 18
    Skill accesses MCP server configuration files (mcp.json). MCP configs contain server URLs, authentication tokens, and tool definitions — reading them allows the skill to discover and potentially abuse other tool integrations.
    Fix: Remove all code or instructions that read MCP configuration files (mcp.json). MCP server details should be managed by the agent runtime, not read by individual skills.
How audits are shown
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.00022 $0.00824
Opus 5 $0.00011 $0.00412
Sonnet 5 $0.00004 $0.00165
Haiku 4.5 $0.00002 $0.00082

Measured 10d ago against content hash 85120d09383f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

source-command-unifi-mcp-update-docs 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.

.agents/skills/source-command-unifi-mcp-update-docs/SKILL.md · 144 lines

How it starts

The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.

source-command-unifi-mcp-update-docs

Use this skill when the user asks to run the migrated source command unifi-mcp-update-docs.

Command Template

Automatically generate and update API.md documentation from tool docstrings and code.

This command scans all MCP tools and resources, extracts documentation from code, and updates API.md to ensure it stays in sync with the implementation.

Steps to execute:

  1. Discover all MCP tools:

    • Scan src/tools/ directory for all tool modules
    • Import each module and extract tool functions
    • Parse docstrings to get:
      • Description
      • Parameters with types and descriptions
      • Return values
      • Raises (errors)
      • Example usage
  2. Discover all MCP resources:

    • Scan src/resources/ directory for resource handlers
    • Extract resource URI templates
    • Document available operations (list, read, subscribe)
  3. Categorize tools by functionality:

    • Site Management
    • Device Operations
    • Client Management
    • Network Configuration
    • WiFi/WLAN Management
    • Firewall & Security
    • Port Forwarding
    • DPI (Deep Packet Inspection)
    • Zone-Based Firewall
    • Traffic Flows
    • Vouchers
    • Webhooks
  4. Read current API.md to preserve:

    • Overview and introduction sections
    • Authentication details
    • Rate limiting information
    • Error handling guide
    • Custom examples or notes
  5. Generate updated documentation:

    • Table of contents with all categories

    • Tool documentation for each category:

      ### tool_name
      
      **Description:** Brief description
      
      **Parameters:**
      - `param1` (type): Description
      - `param2` (type, optional): Description
      
      **Returns:** Return value description
      
      **Example:**
      ```json
      {
        "tool": "tool_name",
        "arguments": {
          "param1": "value1"
        }
      }
      
  6. Update API.md:

    • Preserve manual sections (overview, auth, errors)
    • Replace tool documentation sections
    • Add new tools that aren't documented
    • Remove documentation for deleted tools
    • Update version number and last updated date

Read the full file on GitHub · 144 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. 10d ago First seen · 144 lines · 22 tokens per session scan A 85120d09383f

Subscribe to this mod's changes

source-command-unifi-mcp-update-docs is a skill published in the GitHub repository enuno/unifi-mcp-server (247 stars, last pushed 3d ago), licensed Apache-2.0. It adds 22 tokens to every session and 824 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens