release

An agent for releasing a command-line package by updating its version, changelog, Git tag, and published build. It also checks that the published version can be resolved before reporting success.

In plain words
What is it for?
Use it to prepare and publish a CLI package release, create its tag, update release notes, and verify the published version.
Why use it?
It groups the release steps into one process and verifies that the released package is actually available afterward.

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/jaemk/mind/release
Clone the repo
git clone --depth 1 https://github.com/jaemk/mind
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 105 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.00019 $0.00105
Opus 5 $0.00010 $0.00053
Sonnet 5 $0.00004 $0.00021
Haiku 4.5 $0.00002 $0.00011

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

examples/monorepo/packages/cli/agents/release.md · 14 lines

What it actually says

release

Bump the cli package version, update its changelog, tag the commit, and publish the build. Verify the published version resolves before reporting success.

This item lives under packages/cli/, a second subtree listed in [source].roots. Convention scanning runs under each root independently, so this agent and the web skill are both discovered from their own packages.

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 · 14 lines · 0 tokens per session scan A d7935b7e6c1b

Subscribe to this mod's changes

release is an agent published in the GitHub repository jaemk/mind (1 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 105 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.