Hmbown/CodeWhale is an open-source coding agent that runs in the terminal and is written in Rust. Developers use it to inspect repositories, edit files, run commands, and coordinate work with configurable model providers, skills, MCP servers, and approval controls; the catalogue entries extend its available workflows.
Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hmbown/codewhale/codew-release-qa-sweep)<a href="https://agentmods.dev/skills/hmbown/codewhale/codew-release-qa-sweep"><img src="https://agentmods.dev/badge/skills/hmbown/codewhale/codew-release-qa-sweep.svg" alt="Measured on agentmods" height="20"></a>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.1 | $0.00031 | $0.01232 |
| Opus 5 | $0.00015 | $0.00616 |
| Sonnet 5 | $0.00006 | $0.00246 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
codew-release-qa-sweep 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codewhale Release QA Sweep
Run this before claiming any Codewhale release work is "done." A green automated gate sweep plus the three manual QA targets is the evidence bar. No sweep, no "done" — report exactly what was run and the result of each step.
When to use
- Before telling Hunter (or a PR thread) that release work is complete or merge-ready.
- After harvesting/landing PRs into the release branch, before the publish boundary.
- When verifying a release candidate on the real landing branch
(e.g.
<release-branch>), which is often local-only.
Automated gate sweep
Run from the repo root, in order. Stop on the first failure and report it.
# 0. Confirm you are on the real release head, not a main-based assumption.
git branch --show-current # expect e.g. <release-branch>
git status --short # working tree should be clean
# 1. Formatting + stray whitespace/conflict markers
cargo fmt --all --check
git diff --check
# 2. Library/protocol/cli/flow/state tests, locked
cargo test -p codewhale-config -p codewhale-protocol -p codewhale-cli \
-p codewhale-workflow -p codewhale-state --locked
# 3. TUI test binaries, locked
cargo test -p codewhale-tui --bins --locked
# 4. TUI debug build, locked
cargo build -p codewhale-tui --locked
# 5. Release build for the shipped binaries, locked
cargo build --release --locked -p codewhale-cli -p codewhale-tui
# 6. Version-drift gate (workspace ↔ npm ↔ Cargo.lock ↔ changelog ↔ README)
./scripts/release/check-versions.sh
# 7. Binary smoke
./target/release/codewhale --version
If you are validating a PR for landing, also test mergeability against the actual release head, never the main-based clean flag:
git merge-tree $(git merge-base <release-branch> <pr-head>) <release-branch> <pr-head>
A PR that is clean against main can still conflict with the release branch.
Manual QA targets
Unit/build gates do not cover the live TUI. Exercise all three and record what you saw:
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.
- today Changed 6e3cd09b4ab7
- 3d ago Changed c0b57c7f1d6d
- 6d ago First seen · 114 lines · 31 tokens per session scan A b4b05024b8f4
codew-release-qa-sweep is a skill published in the GitHub repository Hmbown/CodeWhale (40,889 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 1,232 once invoked, about $0.0002 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.
Other skills, from other repositories
computer-use
See the screen and operate it. Use when the user asks to click, type, or check something visually on this machine.
do-release
Cut a new nrflo release. Bumps VERSION, generates human-readable release notes from git log, tags, pushes, monitors the GoReleaser and Docker CI runs, then replaces the GitHub Release body with the synthesized notes. Accepts one SemVer bump argument: patch (+0.0.1), minor (+0.1.0), major (+1.0.0).
rustfs-release-publish
Run the end-to-end RustFS console gate, version bump, preview validation, human confirmation, and final-tag publication pipeline. Use only when the user explicitly asks to release or publish a RustFS version (发版/发布).
tutti-app-release
Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow. Use for caller workflows, tutti.app.json manifests, @tutti-os/app-release-tools, S3/CloudFront release hosting, latest.json, versions.json, catalog.json, catalog-only…
changelog-draft
Generate a reviewable changelog draft from PRs merged in a release range. Extracts explicit CHANGELOG markers, classifies unmarked PRs, adds external contributor attribution, and outputs markdown + JSON artifacts. Does NOT mutate channelversions.json.
ship-and-babysit
End-to-end PR shipping workflow for tinyhumansai/openhuman: commit local changes, push to the user's fork, open or reuse a PR against main, then babysit CI and CodeRabbit feedback until the PR is green and clean. Use when the user asks to ship, open a PR, monitor CI, address review comments, or 'babysit' a branch.