unifi-mcp: Skill for Claude Code

.agents/skills/claude-plugin-config-transport/SKILL.md

myco:claude-plugin-config-transport is a skill for Claude Code from devjourney/unifi-mcp. It costs 192 tokens per session (5,007 once invoked), scanned A, a copy of myco:claude-plugin-config-transport, MIT.

A set of instructions for keeping UniFi MCP plugins configured and communicating reliably. MCP is a way for an agent to use external tools; these instructions cover transport settings, startup scripts, shared code, and plugin-only releases.

In plain words
What is it for?
Use it when changing transport.py, transport flags, application configuration files, plugin setup scripts, shared dispatch code, or release metadata for the UniFi plugins.
Why use it?
It helps avoid a transport race that can silently make the plugins' tools disappear, and keeps configuration consistent across the network, Protect, and Access applications.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument; installed under .agents/ (shared by several agents); mentions Codex.

This is devjourney/unifi-mcp's own configuration. It tells Claude Code how to work on unifi-mcp 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 configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash plugins/unifi-network/scripts/check-prereqs.sh.

Reuse

Borrowing it

Nothing to install: this file belongs to devjourney/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.

Copy the file
curl -O https://raw.githubusercontent.com/devjourney/unifi-mcp/main/.agents/skills/claude-plugin-config-transport/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/devjourney/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 myco:claude-plugin-config-transport

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/devjourney/unifi-mcp/claude-plugin-config-transport"><img src="https://agentmods.dev/badge/skills/devjourney/unifi-mcp/claude-plugin-config-transport.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 192 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,007 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 100% copy Near-identical to another mod 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.00192 $0.05007
Opus 5 $0.00096 $0.02504
Sonnet 5 $0.00038 $0.01001
Haiku 4.5 $0.00019 $0.00501

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

Security

Grade A, and why

myco:claude-plugin-config-transport 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.

Origin

This is a copy

100% identical to myco:claude-plugin-config-transport — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/claude-plugin-config-transport/SKILL.md · 358 lines

How it starts

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

Claude Plugin Configuration and Transport Stability

This skill covers the full lifecycle of Claude MCP plugin integration in unifi-mcp: from configuring transport flags correctly, through understanding the asyncio transport architecture that keeps MCP tools available, to verifying plugin setup, writing portable shell scripts, and publishing plugin-only releases. The procedures share a common prerequisite — understanding the uvx launch context — because a wrong flag can trigger a transport race that silently drops all MCP tools with no visible error.

Relevant files:

  • apps/network/src/unifi_network_mcp/config/config.yaml
  • apps/protect/src/unifi_protect_mcp/config/config.yaml
  • apps/access/src/unifi_access_mcp/config/config.yaml
  • plugins/unifi-network/scripts/set-env.sh, plugins/unifi-network/scripts/check-prereqs.sh
  • plugins/unifi-protect/scripts/set-env.sh, plugins/unifi-protect/scripts/check-prereqs.sh
  • plugins/unifi-access/scripts/set-env.sh, plugins/unifi-access/scripts/check-prereqs.sh
  • packages/unifi-mcp-shared/src/unifi_mcp_shared/transport.py
  • packages/unifi-mcp-shared/src/unifi_mcp_shared/strict_dispatch.py
  • .agents/plugins/marketplace.json (multi-target plugin registry: Claude, Codex, OpenClaw)
  • .codex-plugin/ (Codex-specific manifest directory, PR #246)
  • .agents/plugins/openclaw/ (OpenClaw-specific manifest directory, PR #248)

Prerequisites

Before modifying any plugin configuration or transport code:

  1. Understand the uvx launch context. When Claude launches a plugin via uvx, the plugin process is not PID 1. This distinction controls which transport path activates inside transport.py and whether HTTP transport will be enabled. The PID check is in resolve_http_config() in transport.py.
  2. Know all three app directories. Transport and HTTP config changes almost always need to be reflected in apps/network/, apps/protect/, and apps/access/ in parallel. Partial application leaves inconsistent behavior.
  3. Know all three plugin directories. Script and setup changes apply to plugins/unifi-network/, plugins/unifi-protect/, and plugins/unifi-access/. Applying to only one or two creates inconsistent behavior that is nearly impossible for users to diagnose.
  4. Know the multi-target plugin registry and all three runtimes. As of PR #246 (Codex) and PR #248 (OpenClaw), unifi-mcp supports three plugin targets: Claude, Codex, and OpenClaw. Plugin configuration, version sync, and release procedures must account for target-specific manifests and initialization paths.
  5. Hold the current MCP shared package version. Plugin versions are slaved to MCP package tags; know the current tag before planning a release (see Procedure F).
  6. Run check-prereqs.sh first (see Procedure D) before activating any plugin setup change in a live environment.

Read the full file on GitHub · 358 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 · 358 lines · 192 tokens per session scan A 27f09dc49d38

Subscribe to this mod's changes

myco:claude-plugin-config-transport is a skill published in the GitHub repository devjourney/unifi-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 192 tokens to every session and 5,007 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to myco:claude-plugin-config-transport, differing in 6 lines, and is treated as a copy.

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