Borrowing it
Nothing to install: this file belongs to Pipelex/pipelex-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/Pipelex/pipelex-mcp/main/.claude/skills/release/SKILL.mdgit 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/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/pipelex/pipelex-mcp/release"><img src="https://agentmods.dev/badge/skills/pipelex/pipelex-mcp/release.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.00196 | $0.03448 |
| Opus 5.5 | $0.00078 | $0.01379 |
| Sonnet 5.5 | $0.00039 | $0.00690 |
| Haiku 4.5 | $0.00020 | $0.00345 |
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 3d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 3d ago Changed 5cf31064e82c
- 21d ago Changed · -20 lines · -56 tokens per session a2e62f92efbf
- 1mo ago Changed · +32 lines · +76 tokens per session e26e87954d0c
- 1mo ago Changed 875eff8a077b
- 1mo ago Changed 57ce98e7b66d
- 1mo ago Changed · -159 lines · +25 tokens per session 462c210fc892
- 2mo 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 4d ago), with no licence file. It adds 196 tokens to every session and 3,448 once invoked, about $0.0008 per session on Opus 5.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-verification
A release-verification checklist for software versions and packages. It covers changelogs, tests, packaging, installation smoke checks, version-control actions, publishing, and checks after release.
audit-release
A pre-release review assistant that checks whether a software package or plugin is ready to publish.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
release
Skill "release" from Hmbown/Codewhale, covering release, invocation, non-goals and workflow.