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/jpicklyk/task-orchestrator/prepare-releasenpx skills add jpicklyk/task-orchestrator --skill prepare-releasegit 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.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.00095 | $0.04795 |
| Opus 5 | $0.00048 | $0.02397 |
| Sonnet 5 | $0.00019 | $0.00959 |
| Haiku 4.5 | $0.00010 | $0.00479 |
Grade A, and why
prepare-release scanned grade A 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 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.
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 — 556 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.
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
4b. Group meaningful changes by theme
Use only these categories (omit any that have no entries):
- Breaking Changes — removed tool, renamed/removed parameter, incompatible schema change
- New Features — new MCP tool, new operation on existing tool, new config option, new query parameter
- Bug Fixes — incorrect behavior corrected, crash fixed, data integrity issue resolved
- Performance — measurable throughput or latency improvement
- Documentation — user-visible docs (only if substantive)
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 First seen · 556 lines · 95 tokens per session scan A d5b386e10b16
prepare-release is a skill published in the GitHub repository jpicklyk/task-orchestrator (205 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 4,795 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (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
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…
lov-release-via-cicd
Configure CI/CD and publish new versions for Node, Tauri, Vite, shell, and GitHub Release projects. Use when the user asks to setup release workflow, publish a new version, verify macOS signing/notarization, recover a failed GitHub Release, or mentions "release-via-cicd", "配置并发布新版", "签名", "notarize", "GitHub 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.
swarm-release
Full SwarmAI release cycle: preflight checks, version bump, binary build, desktop package, smoke test, and GitHub publish. The single release path — handles version bump + tag plus build/package/smoke stages. TRIGGER: "release", "cut release", "ship it", "发版". NOT FOR: sswarm-build, shive-manager use cases.
ci-cd-supply-chain
Use this capability for Git workflow, pull request policy, branch protection, CI/CD, build pipelines, release automation, dependency management, SBOM, provenance, SLSA, signing, container scanning, lockfiles, and supply-chain security. Trigger on CI, CD, pipeline, Git, branch, PR, release, dependency, SBOM…
finish-task
Close out the current task — verify all steps done, sync spec, fill completion notes, update worklog, and handle git (commit / push / PR per config).