A release procedure for the Bashunit project that validates changes, builds the project, updates its records, and publishes a version.

Use it to preview or perform a release, choose a version from the unreleased changes, run tests and static checks, and publish the resulting build.

It checks that tests and quality checks pass before release and keeps versioning, checksums, changelog entries, tags, and publishing steps consistent.

release — Skill by TypedDevs

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 skills/typeddevs/bashunit/release

Any agent

npx skills add TypedDevs/bashunit --skill release

Clone the repo

git clone --depth 1 https://github.com/TypedDevs/bashunit

Made for: Claude Code, Codex.

Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 645 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.

Model	Per session	Once invoked
Fable 5	$0.00011	$0.00645
Opus 5	$0.00005	$0.00322
Sonnet 5	$0.00002	$0.00129
Haiku 4.5	$0.00001	$0.00064

Measured 2d ago against content hash 38474ecf1c33, 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.

.claude/skills/release/SKILL.md · 81 lines

How it starts

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

Release

Thin reminder around ./release.sh. The release script owns the whole end-to-end flow (version bumps, build, checksum, CHANGELOG, commit, signed tags, push, GitHub release, latest branch). Don't reimplement those steps here — fix release.sh if something is missing.

Current State

Current version: !grep -o 'BASHUNIT_VERSION="[^"]*"' bashunit | cut -d'"' -f2
Branch: !git branch --show-current
Working tree: !git status --short
Unreleased changes: !awk '/^## Unreleased$/,/^## \[/' CHANGELOG.md | head -30

Steps

1. Pre-flight

./bashunit tests/                 # all green
make sa && make lint              # static analysis + editorconfig
gh run list --limit 3 --branch main

Stop and report if anything fails. Don't release on a red main.

2. Pick the version

$ARGUMENTS overrides; otherwise the script auto-increments the minor. Bump by the Unreleased section: a ### Added/feat → minor, only ### Fixed → patch. Confirm the version with the user before publishing.

3. Preview, then publish

./release.sh <version> --dry-run   # preview; changes nothing
./release.sh <version> --force     # publish (non-interactive)

Notes:

--dry-run release notes look "off" (they show the previous version's section) because the CHANGELOG isn't actually rewritten in a dry run. The real run converts ## Unreleased → ## [<version>] first, so the published notes are correct. Not a bug.
Tagging is gpgsign-safe: release::create_tags makes annotated, -m tags (signed when tag.gpgsign=true) and pins v0 to the release commit (^{}). No manual tagging needed.
npm publishes automatically via .github/workflows/npm-publish.yml on the GitHub release: published event.

4. Verify the published artifacts

gh release view <version>                       # assets: bin/bashunit + bin/checksum
gh run list --workflow npm-publish.yml --limit 1
git log --oneline -1 origin/latest             # latest branch advanced (docs deploy)

Read the full file on GitHub · 81 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.

2d ago First seen · 81 lines · 11 tokens per session scan A 38474ecf1c33

Subscribe to this mod's changes

release is a skill published in the GitHub repository TypedDevs/bashunit (424 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 645 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-30.

Git and workflow Testing assertions bash bash-script testing-framework unittesting

x-nets

Enhanced netstat module with cached data and structured output. View network connections, routing tables, and interface statistics in interactive or TSV/CSV formats. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 69 tokens

x-mankier

Search and browse man pages from ManKier.com. Command line interface for ManKier man page repository. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 62 tokens

x-osv

CLI for Google OSV database. Query vulnerabilities for packages, scan local projects for vulnerable dependencies. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill). Required Tool: Install osv-scanner for project scanning (see https://github.com/google/osv-scanner).

x-cmd/x-cmd · 72 tokens

release