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/monorepo-release-pipeline/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/monorepo-release-pipeline)<a href="https://agentmods.dev/skills/sirkirby/unifi-mcp/monorepo-release-pipeline"><img src="https://agentmods.dev/badge/skills/sirkirby/unifi-mcp/monorepo-release-pipeline/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/monorepo-release-pipeline"><img src="https://agentmods.dev/badge/skills/sirkirby/unifi-mcp/monorepo-release-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 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 Tool Misuse · line 234 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 Tool Misuse · line 234 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.
- low MCP Rug Pull · line 56 pip install without ==version installs the latest release, which could include malicious changes.Fix: Pin the version: pip install package==1.2.3
- low MCP Rug Pull · line 313 pip install without ==version installs the latest release, which could include malicious changes.Fix: Pin the version: pip install package==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.00210 | $0.10240 |
| Opus 5.5 | $0.00084 | $0.04096 |
| Sonnet 5.5 | $0.00042 | $0.02048 |
| Haiku 4.5 | $0.00021 | $0.01024 |
Grade C, and why
myco:monorepo-release-pipeline scanned grade C 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 13d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/wheelcheck && mkdir -p /tmp/wheelcheck Copies of this mod
1 near-identical copy found in the catalogue:
- myco:monorepo-release-pipeline — 98% identical, 318 lines differ
How it starts
The opening of the file, as written. The whole thing — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo Release Pipeline
The unifi-mcp repo ships seven independently versioned Python packages plus the
Node/TypeScript worker app: unifi-core
and unifi-mcp-shared live under packages/; unifi-network-mcp, unifi-protect-mcp,
unifi-access-mcp, and unifi-api-server live under apps/; unifi-mcp-relay lives under packages/
alongside core and shared; unifi-mcp-worker lives under apps/worker/ and publishes to npm.
Each has its own package identity, tag namespace, publish workflow, and release-notes scope. Getting the release sequence wrong leaves downstream
packages referencing non-existent PyPI versions or produces contaminated release notes
that bleed across package boundaries.
Prerequisites
- All feature PRs for the release are merged to
main. - PRs that change any package's
pyproject.tomlorsrc/must pass the pin-alignment CI gate (automated blocker). The gate builds the workspace wheels and installs them the way a user would, so a downstream floor that cannot work on PyPI fails before release. See Procedure D, Step 0 for exactly what it covers and what it cannot see. - Working tree is clean:
git statusshows nothing staged or modified. - Remote is current:
git fetch origin && git log origin/main..HEADshows nothing. - PyPI credentials are not stored locally — publishing is handled entirely by
GitHub Actions OIDC trusted publishing (no
TWINE_PASSWORD, noPYPI_TOKEN). - Decide which packages are changing and their new versions before pushing any tag.
Package Map
| Package | Directory | PyPI Name | Tag namespace |
|---|---|---|---|
unifi-core |
packages/unifi-core/ |
unifi-core |
core/v* |
unifi-mcp-shared |
packages/unifi-mcp-shared/ |
unifi-mcp-shared |
shared/v* |
unifi-mcp-network |
apps/network/ |
unifi-network-mcp |
network/v* |
unifi-mcp-protect |
apps/protect/ |
unifi-protect-mcp |
protect/v* |
unifi-mcp-access |
apps/access/ |
unifi-access-mcp |
access/v* |
unifi-api-server |
apps/api/ |
unifi-api-server |
api/v* |
unifi-mcp-relay |
packages/unifi-mcp-relay/ |
unifi-mcp-relay |
relay/v* |
unifi-mcp-worker |
apps/worker/ |
unifi-mcp-worker (npm, unscoped) |
worker/v* |
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.
- 13d ago Changed · +4 lines 57b9c3d130d1
- 14d ago Changed · +22 lines 7ad9af030d25
- 15d ago Changed · +97 lines · +25 tokens per session d32bc344899e
- 1mo ago Changed · +68 lines · -9 tokens per session fa1d36d07d46
- 1mo ago Changed · +2 lines eecfc80dc113
- 1mo ago Changed · +12 lines 8cab9aab1f5f
- 1mo ago First seen · 412 lines · 194 tokens per session scan C 3bb9a75a33e7
myco:monorepo-release-pipeline is a skill published in the GitHub repository sirkirby/unifi-mcp (955 stars, last pushed yesterday), licensed MIT. It adds 210 tokens to every session and 10,240 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
github-ops
GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git…
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers the Changelog line from each PR merged since the last stable tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.