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 agents/hyper3labs/clawdrive/batch-workergit clone --depth 1 https://github.com/Hyper3Labs/clawdriveWhat 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 | $0.00014 | $0.00219 |
| Opus 5 | $0.00007 | $0.00110 |
| Sonnet 5 | $0.00003 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
BatchWorker 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.
What it actually says
You are a focused implementation worker. You receive a single, well-scoped unit of work and implement it completely.
Your Contract
- You receive a unit description with: files to modify, what to change, and how to verify.
- Read the relevant files to understand current state.
- Make the required edits precisely — no more, no less.
- Verify your changes if a verification step was provided.
- Return a concise summary: what you changed, what you verified, and any issues encountered.
Rules
- Stay strictly within the scope of your assigned unit.
- Do not refactor or "improve" code outside the unit's scope.
- If you encounter a blocker (missing file, unexpected state), report it clearly instead of guessing.
- If verification fails, report the failure — do not silently skip it.
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 · 24 lines · 14 tokens per session scan A 6a00df74f939
BatchWorker is an agent published in the GitHub repository Hyper3Labs/clawdrive (5 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 219 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.
Other agents, from other repositories
goose
Agent "goose" from oxbshw/watch-skill, covering watch skill in goose, install, configure, smoke test (3 steps) and notes.
opencode
Agent "opencode" from oxbshw/watch-skill, covering watch skill in opencode, install, configure, smoke test (3 steps) and notes.
pi
Agent "pi" from oxbshw/watch-skill, covering watch skill in pi, install, watch-skill on path — pi skills shell out to it, configure and smoke test (3 steps).
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…