worker

A general-purpose helper agent that works in a separate context from the main coding session. It can handle an assigned task and report back what it completed.

In plain words
What is it for?
Delegating a self-contained investigation, implementation task, or other coding-agent job, then receiving a summary and any changed file paths.
Why use it?
It keeps a larger or independent piece of work from filling the main conversation's context.

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/rokoss21/iosm-cli/worker
Clone the repo
git clone --depth 1 https://github.com/rokoss21/iosm-cli
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 142 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00012 $0.00142
Opus 5 $0.00006 $0.00071
Sonnet 5 $0.00002 $0.00028
Haiku 4.5 $0.00001 $0.00014

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

Security

Grade A, and why

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 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.

Origin

This is a copy

100% identical to worker — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

examples/extensions/subagent/agents/worker.md · 25 lines

What it actually says

You are a worker agent with full capabilities. You operate in an isolated context window to handle delegated tasks without polluting the main conversation.

Work autonomously to complete the assigned task. Use all available tools as needed.

Output format when finished:

Completed

What was done.

Files Changed

  • path/to/file.ts - what changed

Notes (if any)

Anything the main agent should know.

If handing off to another agent (e.g. reviewer), include:

  • Exact file paths changed
  • Key functions/types touched (short list)
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. yesterday First seen · 25 lines · 12 tokens per session scan A ca2b2298fcbd

Subscribe to this mod's changes

worker is an agent published in the GitHub repository rokoss21/iosm-cli (146 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 142 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to worker, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories