Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mikeparcewski/wicked-gardennpx agentmods add commands/mikeparcewski/wicked-garden/wg-releaseWrote 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/mikeparcewski/wicked-garden/wg-release)<a href="https://agentmods.dev/commands/mikeparcewski/wicked-garden/wg-release"><img src="https://agentmods.dev/badge/commands/mikeparcewski/wicked-garden/wg-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/mikeparcewski/wicked-garden/wg-release"><img src="https://agentmods.dev/badge/commands/mikeparcewski/wicked-garden/wg-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.00668 |
| Opus 5 | $0.00000 | $0.00334 |
| Sonnet 5 | $0.00000 | $0.00134 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
wg-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 10d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release the wicked-garden plugin with version management and changelog generation.
Arguments
Parse the provided arguments: $ARGUMENTS
- --bump [type]: Specify version bump (major, minor, patch)
- --dry-run: Preview changes without applying them
- --version [X.Y.Z]: Set specific version
- --no-tag: Skip git tag creation
Step 1: Quality Gate
Before any release, run the full quality check:
/wg-check --full
If /wg-check --full reports NEEDS WORK:
- Review each issue identified
- For each issue, delegate to the appropriate specialist agent to resolve it (e.g., engineering for code issues, product for description/value issues, qe for test issues)
- After specialists resolve issues, re-run
/wg-check --fullto confirm READY - Do NOT proceed to Step 2 until the check passes
Step 2: Version Analysis
If arguments are provided with a bump type, use them directly.
If no bump type is provided, enter interactive mode:
- Show current version from
.claude-plugin/plugin.json - Analyze commits since last release
- Suggest version bump based on commit messages
- Ask for confirmation before proceeding
Semantic Versioning Rules
Version format: MAJOR.MINOR.PATCH
Auto-detection from commits:
BREAKING CHANGE:,feat!:,fix!:→ major bumpfeat:,feature:→ minor bumpfix:,bugfix:→ patch bumpdocs:,chore:,refactor:→ no bump (but included in changelog)
Step 3: Release
Run the release script targeting the repo root:
python3 .claude/skills/releasing/scripts/release.py . $ARGUMENTS
Release Process
- Collect commits since last tag
- Categorize commits by type
- Determine version bump
- Update version in
.claude-plugin/plugin.json - Update version in
.claude-plugin/marketplace.json - Generate/update
CHANGELOG.mdat repo root - Create git tag (unless --no-tag)
- Create GitHub release with release notes via
gh release create
Step 4: Push & Verify
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.
- 10d ago First seen · 93 lines · 0 tokens per session scan A 09b0f327e26e
wg-release is a command published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 668 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-31.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.