agentmods.dev

release

A release-preparation command for a Python project.

In plain words
What is it for?
Use it to check linting, type checking, and tests; update CHANGELOG.md and pyproject.toml; and display the git commands for publishing a release.
Why use it?
It organizes version changes, changelog dates, comparison links, and verification checks while leaving the final git commit, tag, and push for the user.

Command for Claude Code

0 15d ago A scan 0 tokens original MIT
View the source file sandeep-alluru/groundcrew
Install

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.

agentmods
npx agentmods add commands/sandeep-alluru/groundcrew/release
Clone the repo
git clone --depth 1 https://github.com/sandeep-alluru/groundcrew

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 219 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00219
Opus 5 $0.00000 $0.00110
Sonnet 5 $0.00000 $0.00044
Haiku 4.5 $0.00000 $0.00022

Measured 2d ago against content hash 7ec9d53abf43, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

  • release — 100% identical, 0 lines differ
  • release — 100% identical, 0 lines differ
  • release — 100% identical, 0 lines differ
  • release — 100% identical, 0 lines differ
  • release — 100% identical, 0 lines differ
  • release — 100% identical, 0 lines differ
  • release — 100% identical, 0 lines differ
  • release — 100% identical, 0 lines differ
.claude/commands/release.md · 22 lines

What it actually says

Prepare a release: bump version, finalize CHANGELOG, and show the git tag command.

Usage: /project:release (e.g. /project:release 0.2.0)

Steps:

  1. Verify all checks pass: lint, typecheck, tests (run make all)
  2. In CHANGELOG.md:
    • Rename [Unreleased] to [] - <today's date in YYYY-MM-DD>
    • Add a new empty [Unreleased] section at the top
    • Update the comparison links at the bottom
  3. In pyproject.toml: set version = ""
  4. Show the git commands needed (do NOT run them): 
    git add CHANGELOG.md pyproject.toml
git commit -m "chore: release v<version>"
git tag v<version>
git push origin main --tags
  5. Note: the GitHub Actions release.yml will auto-publish to PyPI on tag push.

Do NOT push or tag without explicit user confirmation.

Changes

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.

  1. 2d ago First seen · 22 lines · 0 tokens per session scan A 7ec9d53abf43

Subscribe to this mod's changes

release is a command published in the GitHub repository sandeep-alluru/groundcrew (0 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 219 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.

Git and workflowLLMReleasesai-agentsautomationcomputer-usemcporacle
Related

Other commands, from other repositories

CHANGELOG

Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.

bytedance/UI-TARS-desktop · 0 tokens

release

Prepare a release: bump version, finalize CHANGELOG, and show the git tag command.

sandeep-alluru/clickproof · 0 tokens

review-renovate

Review and merge renovate PRs with automerge configuration updates.

liam-hq/liam · 11 tokens

release

Perform a full release: generate release notes, bump version, commit, tag, and push.

elirantutia/vibeyard · 0 tokens

release

Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.

swingerman/ha-dual-smart-thermostat · 29 tokens

SHIP_RELEASE

Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.

Osiris-DevWorks/smart-citizen · 34 tokens