Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/pipelex/pipelex-mcp/releasenpx skills add Pipelex/pipelex-mcp --skill releasegit clone --depth 1 https://github.com/Pipelex/pipelex-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/pipelex/pipelex-mcp/release)<a href="https://agentmods.dev/skills/pipelex/pipelex-mcp/release"><img src="https://agentmods.dev/badge/skills/pipelex/pipelex-mcp/release.svg" alt="Measured on agentmods" 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 | $0.00151 | $0.02876 |
| Opus 5 | $0.00076 | $0.01438 |
| Sonnet 5 | $0.00030 | $0.00575 |
| Haiku 4.5 | $0.00015 | $0.00288 |
Grade A, and why
release 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pipelex-mcp Release Workflow
This skill handles the full release cycle for both distributions of
pipelex-mcp: the public @pipelex/mcp npm package (local workshop) and the
Skybridge server deployed through Alpic (hosted console). A "release" means:
bump their one shared version, finalize the changelog, get it onto main
through a release/vX.Y.Z branch, then publish and deploy the same main
commit before tagging it.
The npm package and Alpic deployment are released in lockstep. They always use
the same package.json version and the same source commit, so "what is live?"
has one answer. Publishing is deliberately not transactional: if one finishing
step fails transiently after the other succeeds, retry it at the same version
and commit. If a permanent code or configuration defect makes that commit
unshippable, deprecate an already-published npm version, fix forward, and cut a
new version from the corrective commit for both surfaces.
Every step is interactive — confirm with the user before mutating files, and never push or open a PR without explicit approval.
Branch flow (read this first — it differs from the sibling TS repos)
pipelex-mcp uses a three-tier flow enforced by .github/workflows/guard-branches.yml:
work-branch (fix/ feature/ refactor/ chore/ docs/ ci-cd/ changelog/ codex/)
→ dev
→ release/vX.Y.Z
→ main
The CI gate only lets a release/vX.Y.Z branch merge into main — dev
can no longer target main directly. That is exactly why this skill exists: the
release branch is the carrier that promotes everything on dev plus the
version-bump commit onto main.
Three CI checks will validate the PR to main, so getting them right here is
what makes the release mergeable:
guard-branches.yml— the head branch must matchrelease/vX.Y.Z(same repo).version-check.yml—package.jsonversion must equal theX.Y.Zin the branch name and be strictly greater thanmain's current version.changelog-check.yml—CHANGELOG.mdmust contain a## [X.Y.Z]entry (note: novprefix in the heading — see the version-string rules below).
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.
- 2d ago First seen · 241 lines · 151 tokens per session scan A 0f4f4691d172
release is a skill published in the GitHub repository Pipelex/pipelex-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 151 tokens to every session and 2,876 once invoked, about $0.0008 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-31.
Other skills, from other repositories
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.
publish-registry
Publish @agentos-software/ registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.