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 fleet-managergit 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/fleet-manager)<a href="https://agentmods.dev/skills/hmbown/codewhale/fleet-manager"><img src="https://agentmods.dev/badge/skills/hmbown/codewhale/fleet-manager/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/fleet-manager"><img src="https://agentmods.dev/badge/skills/hmbown/codewhale/fleet-manager.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.00025 | $0.01087 |
| Opus 5.5 | $0.00010 | $0.00435 |
| Sonnet 5.5 | $0.00005 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
fleet-manager 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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleet Manager
Use this skill when acting as a manager agent for Codewhale fleet runs. Your job is to classify worker state, choose the narrowest safe typed action, and leave a ledgered receipt or a safe escalation draft.
Authority Boundary
- Prefer typed fleet surfaces over shell spelunking:
codewhale fleet status,inspect,logs,artifacts,interrupt,restart,resume,stop(stop requires--all), and the Runtime API endpoints. - Do not read
.codewhale/fleet.jsonl, host logs, or remote files directly unless the typed command or API is missing required evidence. - Do not send Slack, webhook, PagerDuty, email, or chat messages unless the user or run config explicitly authorizes sending. Draft the message instead.
- Never include secrets, tokens, webhook URLs, routing keys, full prompts, or oversized logs in a summary or escalation.
Triage Loop
- Identify the run and worker from the user request, run receipt, or fleet
status output. If no worker is named, start with
codewhale fleet status. - Inspect the worker with
codewhale fleet inspect <worker-id>or the matching Runtime API worker endpoint (GET /v1/fleet/workers/{worker_id}). - Review bounded evidence with
codewhale fleet logs <worker-id>andcodewhale fleet artifacts <worker-id>, or the Runtime API equivalents (GET /v1/fleet/runs/{run_id}/receipts/{task_id}/evidenceandGET /v1/fleet/runs/{run_id}/events/replay). Summarize artifact refs, not full payloads. - Classify the state before acting:
transient failure: transport error, timeout, stale heartbeat, host unavailable, or retryable provider/network failure.task failure: worker completed the task but the result is wrong, missing required artifacts, or reports a domain error.verifier failure: scorer/verifier failed or disagrees with the worker result.needs-human: missing authority, unsafe secret boundary, destructive action, repeated restart exhaustion, ambiguous product decision, or conflict between artifacts and verifier.
- Choose one typed action:
- run has orphaned leases after a manager restart:
codewhale fleet resume <run-id>(idempotent reconcile). - transient and retry budget remains:
codewhale fleet restart <worker-id>. - transient but unsafe to retry: draft escalation and mark needs-human.
- task failure: preserve artifacts, summarize the failure, and avoid restart unless the task spec says retrying can produce new evidence.
- verifier failure: inspect scorer inputs and artifacts, then escalate if the verifier cannot be corrected through a typed action.
- needs-human: do not restart automatically; draft a concise escalation.
- run has orphaned leases after a manager restart:
- Record the result in the response: classification, action taken or drafted, evidence commands, artifact refs, and next owner.
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.
- 1mo ago Changed · +4 lines fa4369c71925
- 1mo ago Changed 312937981cd0
- 1mo ago Changed · -1 tokens per session ffb4af1ea509
- 1mo ago First seen · 107 lines · 26 tokens per session scan A 3a7830613a1b
fleet-manager is a skill published in the GitHub repository Hmbown/CodeWhale (41,099 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 1,087 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.
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-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.
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.