release-patch

A release command for publishing the next patch version of a Go project from its latest semantic version tag. It checks the build workflow, downloadable files, checksums, and installation result.

In plain words
What is it for?
Use it to create and push one annotated patch tag, verify the GitHub Release and GoReleaser files, and confirm that the official installer reports the intended version.
Why use it?
It reduces the chance of publishing an unverified release or tagging a project when the working tree, branch, or continuous-integration checks are not ready.

Command

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/stringke/std-agent/release-patch
Clone the repo
git clone --depth 1 https://github.com/StringKe/std-agent
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 255 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.00017 $0.00255
Opus 5 $0.00009 $0.00128
Sonnet 5 $0.00003 $0.00051
Haiku 4.5 $0.00002 $0.00026

Measured yesterday against content hash 81c1a93513b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

release-patch 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 yesterday.

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.

.grok/commands/release-patch.md · 27 lines

What it actually says

Release patch

目标:从最新 semver tag 发布下一个 patch,且 release workflow、assets、checksum 和安装结果全部可验证。

Preconditions

  • worktree clean,mainorigin/main 一致。
  • main 最新 CI conclusion 为 success
  • 最新 tag 与目标 patch 不冲突。

Release

创建 annotated tag vX.Y.(Z+1) 并仅 push 该 tag。tag push 后不得删除或改写。

Done means

  • .github/workflows/release.yml 成功。
  • GitHub Release 包含预期平台 archive 和 checksum。
  • 官方安装脚本可安装该版本,stdagent version 返回目标 tag。

失败时先修复根因:未 push tag 可停止;已 push tag 优先重跑 workflow,仍需代码修复则发布更高 patch。

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. yesterday First seen · 27 lines · 17 tokens per session scan A 81c1a93513b6

Subscribe to this mod's changes

release-patch is a command published in the GitHub repository StringKe/std-agent (8 stars, last pushed 11d ago), licensed MIT. It adds 17 tokens to every session and 255 once invoked, about $0.0001 per session on Opus 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-31.