unifi-mcp: Skill for Claude Code

.agents/skills/live-smoke-testing/SKILL.md

myco:live-smoke-testing is a skill for Claude Code from sirkirby/unifi-mcp. It costs 185 tokens per session (7,988 once invoked), scanned A, original, MIT.

A test guide and harness for checking UniFi integrations against real UniFi hardware. Smoke tests are focused checks that verify a system works in a real environment, beyond mocked tests.

In plain words
What is it for?
Use it to configure credentials, select test phases, classify tools, and run or debug live checks against UniFi controllers.
Why use it?
It catches authentication, API-version, response-format, and hardware-specific problems that ordinary automated tests may miss.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is sirkirby/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 uv run python scripts/live_smoke.py --server network --phase safe.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/sirkirby/unifi-mcp/main/.agents/skills/live-smoke-testing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/sirkirby/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:live-smoke-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/sirkirby/unifi-mcp/live-smoke-testing/github.svg)](https://agentmods.dev/skills/sirkirby/unifi-mcp/live-smoke-testing)
Your own site
<a href="https://agentmods.dev/skills/sirkirby/unifi-mcp/live-smoke-testing"><img src="https://agentmods.dev/badge/skills/sirkirby/unifi-mcp/live-smoke-testing/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:live-smoke-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/sirkirby/unifi-mcp/live-smoke-testing"><img src="https://agentmods.dev/badge/skills/sirkirby/unifi-mcp/live-smoke-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 185 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,988 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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: 7 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 6
    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 67
    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 177
    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 Tool Misuse · line 55
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
  • high Anti-Refusal · line 69
    Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
    Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
  • medium MCP Rug Pull · line 413
    Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.
    Fix: Pin the image: image:tag or image@sha256:abc123
  • medium MCP Rug Pull · line 514
    Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.
    Fix: Pin the image: image:tag or image@sha256:abc123
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.00185 $0.07988
Opus 5 $0.00093 $0.03994
Sonnet 5 $0.00037 $0.01598
Haiku 4.5 $0.00018 $0.00799

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

Security

Grade A, and why

myco:live-smoke-testing 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 4d 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.

curl -k https://$UNIFI_HOST
.agents/skills/live-smoke-testing/SKILL.md · 533 lines

How it starts

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

Live Smoke Testing Against Real UniFi Hardware

scripts/live_smoke.py is the manifest-driven live hardware test harness. It validates API contracts that mock-based CI (unit tests, golden fixtures) structurally cannot catch — auth token expiry, payload normalization, API version mismatches, and hardware-specific field assumptions. Live smoke runs caught multiple critical bugs before merge. Run live smoke before every major merge that touches API-facing code.

Prerequisites

Before any live run, ensure:

  1. .env file at project root (gitignored) with real credentials:

    UNIFI_HOST=<controller-hostname-or-ip>
    UNIFI_USERNAME=<admin-username>
    UNIFI_PASSWORD=<admin-password>
    UNIFI_SITE=<site-id>           # usually "default"
    # For Access domain:
    UNIFI_ACCESS_API_KEY=<access-api-key>
    
  2. Per-server tools_manifest.json is up-to-date — the harness auto-discovers tools from each server's manifest. During development, verify your local module's manifest is current:

    # Check where each server's manifest is located
    find . -name "tools_manifest.json" -type f
    

    New tools registered in the manifest are automatically included in smoke runs; no manual harness edits are needed just to add read-only or preview coverage for a newly registered tool. If adding a new tool, verify the manifest entry exists and safety_tier() classification is correct (see Procedure A).

  3. Target hardware is reachable — verify connectivity before running:

    curl -k https://$UNIFI_HOST
    
  4. Branch context — the harness lives in scripts/live_smoke.py on the main branch. When branching or bisecting, confirm you have the current harness code before running.

  5. Git worktree .env placementscripts/live_smoke.py derives its repo root from its own file location (Path(__file__).resolve().parents[1]) and loads .env from that root. In a git worktree the root resolves to the worktree directory, NOT the main checkout. Copy or symlink your credentials file from the main checkout into the worktree root before running:

    ln -s /path/to/main-checkout/.env /path/to/worktree/.env
    

    Omitting this causes silent credential-not-found failures with no warning.

Read the full file on GitHub · 533 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. 4d ago Changed · +10 lines b59c08de6d2e
  2. 12d ago First seen · 523 lines · 185 tokens per session scan A 59b5f9c678a8

Subscribe to this mod's changes

myco:live-smoke-testing is a skill published in the GitHub repository sirkirby/unifi-mcp (803 stars, last pushed today), licensed MIT. It adds 185 tokens to every session and 7,988 once invoked, about $0.0009 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-30.