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
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.
npx skills add Hmbown/CodeWhale --skill gh-credit-harvestgit clone --depth 1 https://github.com/Hmbown/CodeWhaleWrote 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/gh-credit-harvest)<a href="https://agentmods.dev/skills/hmbown/codewhale/gh-credit-harvest"><img src="https://agentmods.dev/badge/skills/hmbown/codewhale/gh-credit-harvest/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/gh-credit-harvest"><img src="https://agentmods.dev/badge/skills/hmbown/codewhale/gh-credit-harvest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 65 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00030 | $0.01149 |
| Opus 5 | $0.00015 | $0.00575 |
| Sonnet 5 | $0.00006 | $0.00230 |
| Haiku 4.5 | $0.00003 | $0.00115 |
Grade A, and why
gh-credit-harvest 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 9d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gh-credit-harvest
Harvest exactly one community PR into the real landing branch with full authorship and machine-readable credit, verified green, then thank the contributor. A PR is evidence: judge it from code, tests, comments, and checks, never the title. Do not merge, close, tag, or publish without Hunter's approval — this skill lands a credited commit and posts thanks; the workflow closes the PR.
When to use
- You have approval to land ONE specific community PR into a release branch.
- The PR is not yet on the landing branch (if it is, close-with-credit instead — see
gh-close-issues). - The landing branch may be local-only (e.g.
<release-branch>); a main-based "mergeable" flag does not prove it lands cleanly.
Workflow
- Find the real landing branch (the one Hunter named, not always
main) and fetch the PR head:git switch <release-branch> git fetch origin pull/<N>/head git log -1 --format='%H %an <%ae>' FETCH_HEAD # author to preserve - Review from evidence, not the title. Read the diff, tests, linked issue, comments, and CI:
gh pr view <N> --repo Hmbown/CodeWhale --json title,author,files,statusCheckRollup gh pr diff <N> --repo Hmbown/CodeWhale - Test mergeability against the REAL landing branch (local-only branches lie via the main flag):
git merge-tree $(git merge-base HEAD FETCH_HEAD) HEAD FETCH_HEAD # empty/clean = no conflict - Land it, preferring cherry-pick — it preserves the original author automatically:
git cherry-pick <sha> # one or more commits from FETCH_HEAD - If it conflicts, spans noise, or needs squashing, re-apply the narrow slice and commit with explicit author + credit trailers. Resolve
--authorand the co-author from.github/AUTHOR_MAP(fall back to numeric noreply):
Thegh api users/<handle> --jq '"\(.id)+\(.login)@users.noreply.github.com"' git commit --author="Name <[email protected]>" -m "fix(scope): what changed (#<N>)" \ -m "Harvested from PR #<N> by @<handle>" \ -m "Co-authored-by: Name <[email protected]>"Harvested from PR #<N> by @<handle>line in the body is what.github/workflows/auto-close-harvested.ymlmatches to auto-close with credit once the commit reachesmain. - Format and run the focused tests for the touched crate — only land green:
cargo fmt --all cargo test -p <crate> # the crate(s) the PR touched, not the whole workspace git log -1 --format='%an <%ae>%n%(trailers:key=Co-authored-by)' # credit the human, from .github/AUTHOR_MAP - Post a brief, warm, specific thank-you on the PR — name what the change fixed, no drama. Leave the PR open; the workflow closes it with credit when the commit lands on
main:gh pr comment <N> --repo Hmbown/CodeWhale \ --body "Thank you @<handle> — clean fix for <the specific bug>. Harvested into the v0.8.61 lane with your authorship preserved; it'll auto-close with credit once it reaches main."
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.
- 9d ago Changed 13add3f6ee9f
- 12d ago First seen · 73 lines · 30 tokens per session scan A 5977fc88e8b5
gh-credit-harvest is a skill published in the GitHub repository Hmbown/CodeWhale (40,914 stars, last pushed 5d ago), licensed MIT. It adds 30 tokens to every session and 1,149 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
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.
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-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.
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-handoff
Use when writing a Codewhale takeover prompt, continuation note, or end-of-session summary for another agent or a later session: a paste-ready handoff grounded in live state, with done/suspected/blocked kept separate.