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.
curl -O https://raw.githubusercontent.com/devjourney/unifi-mcp/main/.agents/skills/live-smoke-testing/SKILL.mdgit clone --depth 1 https://github.com/devjourney/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/devjourney/unifi-mcp/live-smoke-testing)<a href="https://agentmods.dev/skills/devjourney/unifi-mcp/live-smoke-testing"><img src="https://agentmods.dev/badge/skills/devjourney/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.
<a href="https://agentmods.dev/skills/devjourney/unifi-mcp/live-smoke-testing"><img src="https://agentmods.dev/badge/skills/devjourney/unifi-mcp/live-smoke-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00185 | $0.06724 |
| Opus 5 | $0.00093 | $0.03362 |
| Sonnet 5 | $0.00037 | $0.01345 |
| Haiku 4.5 | $0.00018 | $0.00672 |
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 9d 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 How it starts
The opening of the file, as written. The whole thing — 477 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:
-
.envfile 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> -
Per-server
tools_manifest.jsonis 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 fNew 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). -
Target hardware is reachable — verify connectivity before running:
curl -k https://$UNIFI_HOST -
Branch context — the harness lives in
scripts/live_smoke.pyon the main branch. When branching or bisecting, confirm you have the current harness code before running. -
Git worktree
.envplacement —scripts/live_smoke.pyderives its repo root from its own file location (Path(__file__).resolve().parents[1]) and loads.envfrom 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/.envOmitting this causes silent credential-not-found failures with no warning.
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.
- 9d ago First seen · 477 lines · 185 tokens per session scan A fb6f5583832a
myco:live-smoke-testing is a skill published in the GitHub repository devjourney/unifi-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 185 tokens to every session and 6,724 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-31.
Other skills, from other repositories
jetson-video-pipeline
Use when executing and verifying Jetson Video Codec SDK or PyNvVideoCodec encode/decode, transcode, segmentation, container decode, AV1, or acceptance workflows with exact artifact handoffs.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
holohub-app-lifecycle
Use for non-failing HoloHub app work with ./holohub: scaffold, build, run, test, visual evidence, lint, and flow benchmarking.
code-plan
Turn a task description and repository into a structured implementation plan (files to create, files to modify, tests to add, risks).
ros2-robotics
Best practices for ROS 2 robotics development, covering package structure, nodes, topics/services/actions, launch files, QoS, tf2 transforms, and testing. Use when creating ROS 2 packages, writing nodes in rclpy or rclcpp, defining custom messages/services/actions, writing launch files, configuring QoS profiles…
SmartHome Video Anomaly Benchmark
VLM evaluation suite for video anomaly detection in smart home camera footage.