release

An agent that manages software release decisions and publication checks for Godpowers packages. A release is the process of preparing and publishing a new software version.

In plain words
What is it for?
Use it to decide whether changes need a minor or major version, and to verify GitHub releases, npm packages, package integrity, and installed behavior.
Why use it?
It keeps version rules, release notes, package sources, integrity records, and installed behavior aligned before a release is considered complete.

Agent

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 agents/hannsxpeter/godpowers/release
Clone the repo
git clone --depth 1 https://github.com/hannsxpeter/godpowers
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 860 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.00860
Opus 5 $0.00000 $0.00430
Sonnet 5 $0.00000 $0.00172
Haiku 4.5 $0.00000 $0.00086

Measured yesterday against content hash 4fa5e5183b42, 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 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.

agents/release.md · 57 lines

How it starts

The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Scope

  • [DECISION] This pillar owns Godpowers version decisions, release readiness, artifacts, and publication truth.

Context

  • [DECISION] The root godpowers package and @godpowers/mcp workspace publish the same semantic version.
  • [DECISION] GitHub releases provide the human-readable notes and immutable tag record; npm registry artifacts and their integrity metadata are the authoritative package source.
  • [DECISION] Tag-triggered GitHub Actions publish both npm packages with provenance.

Decisions

  • [DECISION] Backward-compatible routing, validation, and workflow capability additions use a minor release.
  • [DECISION] Raising a published workspace package's minimum Node.js version or adopting an incompatible protocol major uses a major release for both version-locked packages.
  • [DECISION] The release containing @modelcontextprotocol/server v2 and the @godpowers/mcp Node 20-plus engine is the Godpowers 6.0.0 major line.
  • [DECISION] A release is complete only after GitHub, npm, package integrity, and isolated installed behavior agree.
  • [DECISION] Godpowers 6.2.0 is published from merged main commit 010f02dbccb17fce42107ce39d681adaa4879251 through annotated tag v6.2.0 and provenance workflow 32242093455.
  • [DECISION] npm [email protected] and @godpowers/[email protected] are promoted to latest, and their exact integrity values and shasums are recorded in RELEASE.md.
  • [DECISION] GitHub Release v6.2.0 was published at 2026-08-19T10:25:32Z after PR and merged-main CI passed.
  • [DECISION] Backward-compatible engineering evidence, route authority, and optional operations-pack additions shipped in Godpowers 6.3.0.
  • [DECISION] Godpowers 6.3.0 is published from merged main commit c45d0473ad946fcd7c02a5706b02f51a40ed0d25 through annotated tags, provenance workflows 32272150358 and 32272475321, exact registry verification, GitHub Release creation, and isolated installs.
  • [DECISION] npm [email protected], @godpowers/[email protected], and @godpowers/[email protected] are promoted to latest, and their exact integrity values and shasums are recorded in RELEASE.md.

Read the full file on GitHub · 57 lines

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 · 57 lines · 0 tokens per session scan A 4fa5e5183b42

Subscribe to this mod's changes

release is an agent published in the GitHub repository hannsxpeter/godpowers (5 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 860 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.