Borrowing it
Nothing to install: this file belongs to vscarpenter/gsd-task-manager. 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/vscarpenter/gsd-task-manager/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/vscarpenter/gsd-task-managerWrote 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/commands/vscarpenter/gsd-task-manager/release)<a href="https://agentmods.dev/commands/vscarpenter/gsd-task-manager/release"><img src="https://agentmods.dev/badge/commands/vscarpenter/gsd-task-manager/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/commands/vscarpenter/gsd-task-manager/release"><img src="https://agentmods.dev/badge/commands/vscarpenter/gsd-task-manager/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.00039 | $0.00607 |
| Opus 5.5 | $0.00016 | $0.00243 |
| Sonnet 5.5 | $0.00008 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00061 |
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 2mo 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release
Release the gsd-taskmanager app or MCP server. Replaces the recurring "bump version to N, commit, push, PR, merge, tag, GH release" manual flow.
Inputs
$ARGUMENTS is either:
patch/minor/major— bump the matching SemVer segment ofpackage.json(workspace root).- An explicit version like
9.4.0— pin to that exact value.
Steps
- Branch preflight — confirm working tree is clean (
git status --porcelain). If dirty, ask whether to stash or include changes. - Branch creation — if on
main, createchore/release-<version>. (Theno-main-commits.shhook will block otherwise.) - Version bump — update
package.jsonandpackages/mcp-server/package.jsonif the MCP server is part of the release. Usenpm version --no-git-tag-versionor edit directly. - Verification gate — run
bun typecheck && bun lint && bun run test. Halt if any fail. - Commit —
chore(release): vX.Y.Zwith a body listing the user-visible changes since the previous tag (git log --oneline <prev-tag>..HEAD). - Push and PR — push the branch, open a PR titled
Release vX.Y.Zwith the changelog as the body. - Wait for review or self-merge — if the user has authority, ask whether to merge immediately.
- Tag — after merge,
git fetch origin main,git tag vX.Y.Z,git push origin vX.Y.Z. - GitHub release —
gh release create vX.Y.Z --generate-notes --title "vX.Y.Z". - MCP publish (if applicable) — if the MCP server bumped, run
npm publishfrompackages/mcp-server/(requiresnpm login).
Anti-goals
- Don't run on a dirty working tree without explicit user OK.
- Don't push tags before the version-bump PR is merged.
- Don't publish to npm without user confirmation — that step is hard to reverse.
Verification before declaring done
- Version bump merged on
main. - Tag exists on remote.
- GitHub release page shows the new version.
- If MCP server was published,
npm view gsd-mcp-server versionreturns the new value.
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.
- 2mo ago First seen · 42 lines · 39 tokens per session scan A c015f9e55472
release is a command published in the GitHub repository vscarpenter/gsd-task-manager (40 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 607 once invoked, about $0.0002 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-30.
Other commands, from other repositories
deploy-release
Prepare and verify a staged or production deployment with rollback and smoke checks.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
deploy
Run the complete ClawBridge release process. This is the ONLY way to deploy — follow every step.
devops
You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.
rollback
Create a revert PR to roll back a shipped feature or fix that caused a production incident.