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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Hmbown/CodeWhalenpx agentmods add skills/hmbown/codewhale/codew-release-qa-sweepWrote 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.01315 |
| Opus 5.5 | $0.00012 | $0.00526 |
| Sonnet 5.5 | $0.00006 | $0.00263 |
| Haiku 4.5 | $0.00003 | $0.00131 |
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 27d 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.
How it starts
The opening of the file, as written. The whole thing — 120 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 the maintainer (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
# Core npm workspace tests plus the shared web gate (install web dependencies first).
# check:web checks committed facts before regeneration, then docs, design tokens,
# lint, TypeScript and the production build. These do not replace the Rust gates.
npm test && npm run check:web
# 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:
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.
- 27d ago Changed · +1 lines b6e238ef9be4
- 1mo ago Changed · +5 lines ab0657608f10
- 1mo ago Changed 6e3cd09b4ab7
- 1mo ago Changed c0b57c7f1d6d
- 1mo 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 (41,099 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 1,315 once invoked, about $0.0001 per session on Opus 5.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
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
github
Skill "github" from Hmbown/Codewhale, covering github, when to use, setup, workflow and non-goals.
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
cw-dogfood
Use when a Codewhale change needs proving in the real product, or when asked to build/install/dogfood the local binaries: stamped release build, atomic install, fresh-shell verification, and the manual QA that gates cannot cover.
cw-orient
Use at the start of any Codewhale work session, or when unsure which checkout, branch, or worktree is authoritative: establish live repo truth before reading a plan or editing a file.
cw-slice
Use before writing code for any Codewhale feature, upgrade, or refactor: find the existing owner of the behavior, bound the change to one reviewable slice, and fix the evidence bar before you start.