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 uchicago-dsi/ai-sci-skills --skill claude-code-workergit clone --depth 1 https://github.com/uchicago-dsi/ai-sci-skillsWrote 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/uchicago-dsi/ai-sci-skills/claude-code-worker)<a href="https://agentmods.dev/skills/uchicago-dsi/ai-sci-skills/claude-code-worker"><img src="https://agentmods.dev/badge/skills/uchicago-dsi/ai-sci-skills/claude-code-worker/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/uchicago-dsi/ai-sci-skills/claude-code-worker"><img src="https://agentmods.dev/badge/skills/uchicago-dsi/ai-sci-skills/claude-code-worker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Rogue Agent · line 16 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00111 | $0.02791 |
| Opus 5.5 | $0.00044 | $0.01116 |
| Sonnet 5.5 | $0.00022 | $0.00558 |
| Haiku 4.5 | $0.00011 | $0.00279 |
Grade A, and why
claude-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 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Worker
Use Claude as a write-capable external worker while Codex remains the supervising owner. The worker is conversational across invocations, but it does not inherit the Codex thread or native tool state. Give it a compact, self-contained prompt and verify its work yourself.
Choose Claude Deliberately
Prefer Claude when the task is bounded, isolatable, large enough to repay delegation overhead, and has objective acceptance checks. It is especially useful for multi-file implementation, mechanical migration, and repository audit work when Claude quota is cheaper than Codex quota.
Work locally instead for a trivial edit, a task needing frequent interactive decisions, or work whose main difficulty is supervisor judgment. Do not delegate protected or credential-bearing content, authoritative imaging, source-data mutation, external publication, frozen execution state, or any task that cannot be isolated safely. If repeated parent correction dominates the work, stop delegating that task shape even when Claude quota is free.
Before Launch
- Read the repository's applicable
AGENTS.mdand task instructions yourself. - Choose one concrete, bounded task with an inspectable result.
- Create a dedicated clean Git worktree under the repository's configured worktree root.
Do not point Claude at a shared checkout or an execution checkout bound to a live job.
Do not improvise a second worktree under
/tmp; inspect a baseline withgit showor a worktree created under the configured root. - Create the state directory outside the worktree. Use a protected directory when the prompt or result is private. Keep PHI, credentials and protected clinical text out of the prompt and out of worker-visible paths. De-identified study identifiers -- the accession or subject keys a de-identified cohort is organized by -- are fine, and a worker usually cannot do the work without them.
- Write a self-contained prompt that includes:
- the exact outcome and boundaries;
- relevant user constraints and applicable repository rules;
- current evidence and file paths needed for the task;
- verification expected from the worker;
- exact writable paths, an exploration boundary, and a stopping condition;
- whether it may commit (default: no);
- an instruction to report changed files, checks, findings, and blockers.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · +2 lines · +8 tokens per session 8a216daea580
- 1mo ago Changed · +94 lines 6916d49bf804
- 1mo ago First seen · 121 lines · 103 tokens per session scan A 409ae2257428
claude-code-worker is a skill published in the GitHub repository uchicago-dsi/ai-sci-skills (20 stars, last pushed 4d ago), licensed MIT. It adds 111 tokens to every session and 2,791 once invoked, about $0.0004 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-09-05.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.