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/claude-plugin-config-transport/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/claude-plugin-config-transport)<a href="https://agentmods.dev/skills/sirkirby/unifi-mcp/claude-plugin-config-transport"><img src="https://agentmods.dev/badge/skills/sirkirby/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.
<a href="https://agentmods.dev/skills/sirkirby/unifi-mcp/claude-plugin-config-transport"><img src="https://agentmods.dev/badge/skills/sirkirby/unifi-mcp/claude-plugin-config-transport.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, 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 Privilege Escalation · line 351 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 357 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 24 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
- medium MCP Rug Pull · line 43 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
- medium MCP Rug Pull · line 66 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
- medium MCP Rug Pull · line 72 uvx/uv tool run commands without ==version create a rug-pull risk.Fix: Pin the version: uvx package-name==1.2.3
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.00192 | $0.05055 |
| Opus 5 | $0.00096 | $0.02527 |
| Sonnet 5 | $0.00038 | $0.01011 |
| Haiku 4.5 | $0.00019 | $0.00505 |
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 3d 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:
- myco:claude-plugin-config-transport — 100% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 360 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.yamlapps/protect/src/unifi_protect_mcp/config/config.yamlapps/access/src/unifi_access_mcp/config/config.yamlplugins/unifi-network/scripts/set-env.sh,plugins/unifi-network/scripts/check-prereqs.shplugins/unifi-protect/scripts/set-env.sh,plugins/unifi-protect/scripts/check-prereqs.shplugins/unifi-access/scripts/set-env.sh,plugins/unifi-access/scripts/check-prereqs.shpackages/unifi-mcp-shared/src/unifi_mcp_shared/transport.pypackages/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:
- 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 insidetransport.pyand whether HTTP transport will be enabled. The PID check is inresolve_http_config()intransport.py. - Know all three app directories. Transport and HTTP config changes almost always need to be reflected in
apps/network/,apps/protect/, andapps/access/in parallel. Partial application leaves inconsistent behavior. - Know all three plugin directories. Script and setup changes apply to
plugins/unifi-network/,plugins/unifi-protect/, andplugins/unifi-access/. Applying to only one or two creates inconsistent behavior that is nearly impossible for users to diagnose. - 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.
- 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).
- Run
check-prereqs.shfirst (see Procedure D) before activating any plugin setup change in a live environment.
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.
- 3d ago Changed · +2 lines a29c4564e3e8
- 12d ago First seen · 358 lines · 192 tokens per session scan A 0e930d0db41c
myco:claude-plugin-config-transport is a skill published in the GitHub repository sirkirby/unifi-mcp (809 stars, last pushed yesterday), licensed MIT. It adds 192 tokens to every session and 5,055 once invoked, about $0.0010 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
streamdeck-designer
Design, theme, and author complete Stream Deck layouts for the user's hardware using the streamdeck-mcp tools. Use whenever the user wants a custom Stream Deck setup, asks for a themed deck (e.g. "hello-kitty Twitch deck", "retrowave music controls", "a dev deck for this repo"), wants buttons or dials configured for…
streamdeck-profile
Use this skill when you need to configure Elgato Stream Deck desktop profiles without taking USB control of the hardware.
unifi-udm-pro-mcp
UniFi UDM Pro MCP Server for managing networks, connected clients, Wi-Fi settings, and device health via Model Context Protocol.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.