Borrowing it
Nothing to install: this file belongs to GenWaveLLC/svgmaker-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/GenWaveLLC/svgmaker-mcp/main/.claude/commands/prepare-release.mdgit clone --depth 1 https://github.com/GenWaveLLC/svgmaker-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/commands/genwavellc/svgmaker-mcp/prepare-release)<a href="https://agentmods.dev/commands/genwavellc/svgmaker-mcp/prepare-release"><img src="https://agentmods.dev/badge/commands/genwavellc/svgmaker-mcp/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/commands/genwavellc/svgmaker-mcp/prepare-release"><img src="https://agentmods.dev/badge/commands/genwavellc/svgmaker-mcp/prepare-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.00000 | $0.00491 |
| Opus 5.5 | $0.00000 | $0.00196 |
| Sonnet 5.5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
prepare-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.
What it actually says
Prepare Release
Run all pre-release checks and prepare a version bump for the automated release pipeline.
Step 1: Determine Version
Ask the user what version to release. Show the current version from package.json and ask:
- What type of version bump? Options: patch, minor, major, prerelease (e.g.
1.0.0-rc.1), or custom version string. - If prerelease, ask for the prerelease identifier (e.g.
rc.1,beta.1). - Show what the new version will be before proceeding. Confirm with the user.
Step 2: Check Working Tree
Run git status to verify the working tree is clean (no uncommitted changes). If there are uncommitted changes, warn the user and ask whether to proceed or abort.
Step 3: Bump Version
Update the version in package.json using the appropriate method:
- For patch/minor/major: run
npm version <type> --no-git-tag-version - For prerelease or custom: edit
package.jsondirectly with the exact version string
Step 4: Run Quality Checks
Run these checks sequentially. Stop and report on the first failure:
- Lint:
npm run lint - Format:
npm run format:check— if this fails, runnpm run formatto auto-fix, then re-check - Type Check:
npm run typecheck - Tests:
npm run test - Build:
npm run build - Security Audit:
npm audit --audit-level moderate --omit=dev
If any check fails (except format, which auto-fixes), stop and help the user fix the issue before continuing.
Step 5: Commit and Push
After all checks pass:
- Stage
package.json(and any files changed by formatting) - Create a commit with message:
chore: bump version to <new-version> - Push to the current branch
Step 6: Summary
Print a summary:
- Previous version → New version
- All checks passed
- Branch and commit hash
- Remind the user: "Merge this branch to
mainto trigger the automated release pipeline."
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 · 51 lines · 0 tokens per session scan A 685f555b2669
prepare-release is a command published in the GitHub repository GenWaveLLC/svgmaker-mcp (88 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 491 tokens. 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.
prepare-release compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| prepare-releaseGenWaveLLC/svgmaker-mcp | Command | 88 | yesterday | MIT | A | 0 | Claude Code |
| landgmickel/flow-next | Command | 717 | yesterday | MIT | A | 13 | Claude Code |
| qualityDesko77/claude-code-skills-1c | Command | 90 | yesterday | MIT | A | 18 | Claude Code |
| release-notesOpenHands/extensions | Command | 176 | yesterday | MIT | A | 44 | Claude Code |
| release-managerruvnet/agentic-flow | Command | 838 | yesterday | none | A | 0 | Claude Code |
| create-prdsswift/ion | Command | 5 | yesterday | MIT | A | 28 | Claude Code |
| rally-merge-prddgonzal3/rally | Command | 6 | 3d ago | MIT | A | 0 | Claude Code |