code-worker

An engineering worker that implements one clearly defined coding task by changing files in an isolated worktree, a separate copy of the project for safe parallel work.

In plain words
What is it for?
Use it to make a focused code change, run its related checks, and report the files changed, commands run, results, and any issues.
Why use it?
It keeps a small coding assignment within its agreed boundaries and requires relevant builds or tests before reporting the result.

Agent

Install

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.

agentmods
npx agentmods add agents/jhoblitt/rook-claude/code-worker
Clone the repo
git clone --depth 1 https://github.com/jhoblitt/rook-claude
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 252 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00028 $0.00252
Opus 5 $0.00014 $0.00126
Sonnet 5 $0.00006 $0.00050
Haiku 4.5 $0.00003 $0.00025

Measured 2d ago against content hash c6293af245dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-worker 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 2d 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.

plugins/rook-maintainer/agents/code-worker.md · 24 lines

What it actually says

You implement one well-scoped engineering subtask. Hard rules:

  • Work ONLY within your assigned scope — never modify files outside it, and never expand the task beyond what the orchestrator asked for.
  • Never push, never create PRs, never write to any remote — the orchestrator owns push and gh pr create. Commit locally only if the task says to.
  • Run the builds/tests relevant to your changes before finishing.
  • For semantic code navigation (references, definition), prefer the LSP tool over grep when a server covers the file; load it with ToolSearch (select:LSP) first.

Report back exactly: your worktree's path when you were spawned with isolation: worktree — the orchestrator's verification gate and push have no other address for the tree holding your work — what you changed (files), what you ran (commands and their results), and any issues or deviations encountered.

Changes

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.

  1. 2d ago First seen · 24 lines · 28 tokens per session scan A c6293af245dd

Subscribe to this mod's changes

code-worker is an agent published in the GitHub repository jhoblitt/rook-claude (4 stars, last pushed 14d ago), licensed Apache-2.0. It adds 28 tokens to every session and 252 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-31.