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 agentmods add skills/hmbown/codewhale/gh-assign-issuesnpx skills add Hmbown/CodeWhale --skill gh-assign-issuesgit 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-assign-issues)<a href="https://agentmods.dev/skills/hmbown/codewhale/gh-assign-issues"><img src="https://agentmods.dev/badge/skills/hmbown/codewhale/gh-assign-issues.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.00024 | $0.01013 |
| Opus 5 | $0.00012 | $0.00507 |
| Sonnet 5 | $0.00005 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
gh-assign-issues 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 4d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gh-assign-issues
Retarget or assign a set of Codewhale issues to a milestone and/or owners in
bulk, verifying every one. The milestone (or assignee) change is the signal;
do not narrate it with comments. Use gh for all GitHub
calls.
When to use
- You have a concrete list of issue numbers (e.g. from triage) to move into a
release milestone such as
v0.8.61, or to assign to owners. - A milestone was renamed/created and its issues need re-pointing.
- You finished grouping the inbox and want the queue to reflect it without posting public chatter.
This skill changes milestone/assignee only. It does not close, label, comment, merge, or release. Those stay with the maintainer.
Workflow
-
Confirm the exact milestone title.
gh issue edit --milestonematches by name, so a typo silently fails (or worse, no-ops). Read the real titles and note the starting open-count:gh api repos/Hmbown/CodeWhale/milestones \ --jq '.[] | "\(.number)\t\(.title)\topen=\(.open_issues)\tstate=\(.state)"'Copy the title string verbatim (e.g.
v0.8.61). If the target milestone is missing or closed, stop and ask the maintainer; do not create one. -
Pre-flight each number.
gh issue editwill happily retarget a PR or a closed issue, so screen first. Theurlreveals PR-vs-issue (/pull/vs/issues/); skip anything not OPEN or that is a PR:for N in 3101 3102 3103; do gh issue view "$N" --repo Hmbown/CodeWhale \ --json number,state,url,milestone \ --jq '"\(.number)\t\(.state)\t\(.url)\tmilestone=\(.milestone.title // "none")"' doneFlag any row whose
urlcontains/pull/(it is a PR) or whose state is notOPEN, and exclude it from the loop below. -
Apply the change, one issue at a time, reporting per-issue success. Use
--milestone,--add-assignee, or both:for N in 3101 3102 3103; do if gh issue edit "$N" --repo Hmbown/CodeWhale \ --milestone "v0.8.61" >/dev/null 2>&1; then echo "ok #$N -> v0.8.61" else echo "FAIL #$N (PR? closed? bad milestone title?)" fi done # owners: add --add-assignee handle (do not invent logins)
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.
- 4d ago Changed 660625e88162
- 6d ago First seen · 93 lines · 24 tokens per session scan A 6fe631c1175c
gh-assign-issues is a skill published in the GitHub repository Hmbown/CodeWhale (40,914 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 1,013 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
computer-use
Full desktop control on macOS, Windows, Linux, and HarmonyOS — accessibility-first observation and actions with pixel fallback, screenshots, zoom, screen recording, and switching between registered computers as a default.
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-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-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.