Codewhale is an open-source coding agent that runs in the terminal and can read repositories, edit files, execute commands, and inspect results while pursuing a task. Developers use it with hosted providers or local models, with controls for how much access it receives.
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 cw-landgit 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/cw-land)<a href="https://agentmods.dev/skills/hmbown/codewhale/cw-land"><img src="https://agentmods.dev/badge/skills/hmbown/codewhale/cw-land.svg" alt="Measured on agentmods" height="20"></a>- 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.00044 | $0.01519 |
| Opus 5 | $0.00022 | $0.00759 |
| Sonnet 5 | $0.00009 | $0.00304 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
cw-land 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 yesterday.
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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cw-land
Verified work still has to land without stepping on other writers, losing
contributor credit, or merging past a gate that has not actually passed. This
stage is about the boundary between "it works" and "it is in main" — and about
which of those steps you are allowed to take.
Stage 5 of the loop: cw-orient → cw-slice → cw-gates → cw-dogfood → land → cw-handoff.
When to use
- The change is verified and needs to become a commit, branch, or PR.
- You are landing someone else's PR, harvesting a contributor's work, or
resolving a conflict caused by
mainmoving. - You are about to merge something behind a required gate.
Workflow
-
Choose the landing shape.
- Direct to
mainis permitted for a small coherent change when this checkout is current, clean, and owns the affected files. Local commit permission never implies push, merge, tag, release, or deploy permission. - A worktree is the right safety boundary for conflicting, dirty, stale, or independent work — and for anything that would otherwise fight the dirt you found in cw-orient.
- An integration branch —
integration/<topic>-<pr>-<date>— is the normal path for anything with conflicts or several moving PRs. It is cheaper than rebasing onto amainthat keeps moving, and it leaves the contributor's branch untouched.
- Direct to
-
Commit narrow and build-green. One coherent change per commit; the tree builds at every commit. Put the real verification in the message — actual pass/fail counts, not "tests pass".
-
Preserve credit mechanically, not just politely. Commit authorship and
Co-authored-by:trailers must use the contributor's own GitHub-linked address — GitHub reads neither.github/AUTHOR_MAPnor.mailmapfor the contribution graph; those are project conventions on top. When a contributor's work lands as our commit, it carries both:Harvested from PR #N by @handle Co-authored-by: Name <github-linked-email>That trailer is what lets
auto-close-harvested.ymlclose their PR with credit. Canonical human identities live in.github/AUTHOR_MAP.
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.
- yesterday First seen · 123 lines · 44 tokens per session scan A f3f248248a5d
cw-land is a skill published in the GitHub repository Hmbown/Codewhale (40,915 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,519 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-09-06.
Other skills, from other repositories
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-close-issues
Close resolved Codewhale issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.