Borrowing it
Nothing to install: this file belongs to jpicklyk/task-orchestrator. 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/jpicklyk/task-orchestrator/main/.claude/skills/prepare-release/SKILL.mdgit clone --depth 1 https://github.com/jpicklyk/task-orchestratorWrote 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/jpicklyk/task-orchestrator/prepare-release)<a href="https://agentmods.dev/skills/jpicklyk/task-orchestrator/prepare-release"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/prepare-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/jpicklyk/task-orchestrator/prepare-release"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/prepare-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium Excessive Agency · line 335 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 551 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00095 | $0.07218 |
| Opus 5.5 | $0.00038 | $0.02887 |
| Sonnet 5.5 | $0.00019 | $0.01444 |
| Haiku 4.5 | $0.00010 | $0.00722 |
Grade C, and why
prepare-release scanned grade C with 2 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 5d 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 ~/.claude/plugins/cache/task-orchestrator-marketplace`, then Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://repo1.maven.org/maven2/org/xerial/sqlite-jdbc/maven-metadata.xml" \ How it starts
The opening of the file, as written. The whole thing — 683 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Release
End-to-end release workflow. Reads commits since the last release tag, infers the semver bump, drafts a user-facing changelog, confirms with you, creates a release PR, merges it, verifies CI is green, tags the release, and monitors the Docker build to completion.
Usage: /prepare-release
Run this from any branch after all feature PRs have been merged to main.
Steps 1-11 are the ordinary point-release path (3.x and 4.x). A major release that lands a long-lived
branch on main follows "Major release landing (X1, first used for 4.0.0)" below instead of Steps 1, 7, 10
and 11b-11e.
Step 1 — Ensure Clean Main
Switch to main and pull latest:
git checkout main
git pull origin main
git status
If git status shows uncommitted changes, stop and resolve them before continuing. The
working tree must be clean.
Step 2 — Find Last Release Tag
git describe --tags --abbrev=0
Note this as LAST_TAG (e.g., v2.0.2). All commits after this tag are candidates for
the release.
If this command fails (no tags exist yet), use the full history — note the first commit hash as the baseline and treat the release as the initial version.
Step 3 — Gather Commits Since Last Tag
git log <LAST_TAG>...HEAD --oneline
git diff <LAST_TAG>...HEAD --stat
git diff <LAST_TAG>...HEAD --name-only
Collect the full output of each. Do not truncate.
Step 4 — Filter and Synthesize (Critical Reasoning Step)
This is not a raw dump of commit messages. Analyze the material and produce a curated, user-facing summary.
4a. Discard internal-only commits
Ignore commits that match any of the following:
- Subject starts with:
wip,WIP,checkpoint,fixup!,chore: rebase,Merge branch,version bump,release: - Commit only touches:
build.gradle.kts,gradle/,*.properties,.gitignore,.github/,Dockerfile,docker-compose.yml,scripts/,*.mdfiles with no API impact - Subject is a bare file list or CI housekeeping note
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.
- 5d ago Changed · +94 lines scan A → C 659fcfb3a11e
- 24d ago Changed 4d4434c9a05e
- 29d ago Changed · +2 lines 035eff552bc8
- 1mo ago Changed · +31 lines 61f29a7d3be5
- 1mo ago First seen · 556 lines · 95 tokens per session scan A d5b386e10b16
prepare-release is a skill published in the GitHub repository jpicklyk/task-orchestrator (210 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 7,218 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
ci-cd-ops
CI/CD pipeline patterns with GitHub Actions, release automation, and testing strategies. Use for: github actions, workflow, CI, CD, pipeline, deploy, release, semantic release, changesets, goreleaser, matrix, cache, secrets, environment, artifact, reusable workflow, composite action.
lov-release-via-cicd
A release workflow for Node, Tauri, Vite, shell, and GitHub Release projects. It checks or configures automated versioning and publishing, including macOS signing and notarisation when relevant.
release
This skill should be used when the user asks about "release process", "versioning", "semantic versioning", "semver", "release automation", "publishing", "package publishing", "release checklist", "version bump", "release notes", or needs guidance on release workflows and version management.
prepare-release
Prepare a version release — follows project release config in .aicontext/release.md, runs first-time setup if config is missing.