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-find-prsgit 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-find-prs)<a href="https://agentmods.dev/skills/hmbown/codewhale/gh-find-prs"><img src="https://agentmods.dev/badge/skills/hmbown/codewhale/gh-find-prs/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-find-prs"><img src="https://agentmods.dev/badge/skills/hmbown/codewhale/gh-find-prs.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 72 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.00027 | $0.01384 |
| Opus 5 | $0.00014 | $0.00692 |
| Sonnet 5 | $0.00005 | $0.00277 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade A, and why
gh-find-prs 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 7d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gh-find-prs
Survey the open PR queue and assign each PR a disposition — backed by code, tests, and checks, never by title — testing real mergeability against the actual release branch (often local-only, e.g. <release-branch>), not the main-based GitHub flag.
When to use
- A maintainer asks "what's in the PR queue?", "what can we land?", or "triage open PRs".
- Before a release cut, to sweep community contributions into the active release branch.
- Whenever you need a per-PR DIRECT-MERGE / HARVEST / DEFER / CLOSE-WITH-NOTE call with credit attached.
This is read-and-recommend. You do NOT merge, close, tag, or publish. You surface evidence and a proposed disposition; the maintainer approves.
Workflow
-
Inventory the queue. One call, structured:
gh pr list --repo Hmbown/CodeWhale --state open \ --json number,title,author,headRefName,baseRefName,isDraft,mergeStateStatus,statusCheckRollupNote
mergeStateStatus(CLEAN / BLOCKED / DIRTY / UNKNOWN) but treat it as a hint only — it is computed againstmain, and the real landing target is usually a different branch. -
Identify the real landing branch. The release head is frequently local-only:
git branch --list 'codex/v0.8*' 'codex/v0.9*' git log --oneline -1 <release-branch>Use that ref, not
main, for every mergeability test below. -
Read each candidate from code, not title. For every non-trivial PR:
gh pr view <N> --repo Hmbown/CodeWhale \ --json files,additions,deletions,statusCheckRollup,body,comments gh pr diff <N> --repo Hmbown/CodeWhaleRead the diff. A "fix(exec): ..." can be a no-op or a regression; a "chore" can be the real fix. Judge the change, the tests it adds, and any review comments.
-
Decode check failures — distinguish trivial from real. In
statusCheckRollup, find eachconclusion: FAILUREand read its job. Codewhale's CI jobs areLint,Test (ubuntu-latest|macos-latest|windows-latest),Version drift,gate(Contribution gate),npm wrapper smoke,Mobile runtime smoke,Documentation,GitGuardian Security Checks.- A
Lintfailure that is onlycargo fmtdrift is trivial — harvestable, fix on landing withcargo fmt --all. - A failing
Test (...)orclippyunder Lint is real — read the log before trusting it. Version driftfailing on a community PR is expected (they bumped, or didn't); not a blocker for harvest.
cargo fmt --all -- --check && cargo clippy --workspace --all-targets - A
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.
- 7d ago Changed 9295b222f40c
- 10d ago First seen · 79 lines · 27 tokens per session scan A 79babd7a705b
gh-find-prs is a skill published in the GitHub repository Hmbown/CodeWhale (40,914 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 1,384 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.
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-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-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-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.