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/monorepo-release-pipeline/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/monorepo-release-pipeline)<a href="https://agentmods.dev/skills/devjourney/unifi-mcp/monorepo-release-pipeline"><img src="https://agentmods.dev/badge/skills/devjourney/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/devjourney/unifi-mcp/monorepo-release-pipeline"><img src="https://agentmods.dev/badge/skills/devjourney/unifi-mcp/monorepo-release-pipeline.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.00194 | $0.05871 |
| Opus 5 | $0.00097 | $0.02936 |
| Sonnet 5 | $0.00039 | $0.01174 |
| Haiku 4.5 | $0.00019 | $0.00587 |
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 11d 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 This is a copy
98% identical to myco:monorepo-release-pipeline — 35 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.
How it starts
The opening of the file, as written. The whole thing — 393 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. - All PRs targeting main must pass the pin-alignment CI gate (automated blocker). This gate runs on every PR and blocks stale transitive dependency pins that would cause fresh installs to fail. See Procedure D, Step 0 for details.
- 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.
- 11d ago First seen · 393 lines · 194 tokens per session scan C d00e5e14ef4c
myco:monorepo-release-pipeline is a skill published in the GitHub repository devjourney/unifi-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 194 tokens to every session and 5,871 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 98% identical to myco:monorepo-release-pipeline, differing in 35 lines, and is treated as a copy.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".