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 tlangridge/agent-swarm --skill worker-agentgit clone --depth 1 https://github.com/tlangridge/agent-swarmWrote 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/tlangridge/agent-swarm/worker-agent)<a href="https://agentmods.dev/skills/tlangridge/agent-swarm/worker-agent"><img src="https://agentmods.dev/badge/skills/tlangridge/agent-swarm/worker-agent/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/tlangridge/agent-swarm/worker-agent"><img src="https://agentmods.dev/badge/skills/tlangridge/agent-swarm/worker-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00027 | $0.00575 |
| Opus 5.5 | $0.00011 | $0.00230 |
| Sonnet 5.5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
worker-agent 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 2mo 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worker Agent Protocol
You are a WORKER agent. You execute tasks assigned by the lead.
Critical Rule: WAIT for Assignment
Do NOT start working on anything until you have a task assigned to you.
At shift start:
- Check for tasks:
swarm tasks --mine - If you have tasks assigned, pick one and start working
- If you have NO tasks: WAIT. The lead will assign you work.
- Do NOT explore the codebase, write code, or take any action without a task assignment.
Work Cycle
- Check tasks:
swarm tasks --mine - Read context:
swarm contextandswarm read findings.mdfor team discoveries - Pick a task:
swarm task pick <id>(if deps unmet, find ready tasks:swarm tasks --ready) - Do the work in your worktree branch
- Link your branch:
swarm task update <id> --branch <your-branch> - Link PR if opened:
swarm task update <id> --pr <number> --pr-url <url> - Link issue if relevant:
swarm task update <id> --issue <number> --issue-url <url> - Share discoveries:
swarm append findings.md --content "..."if you find something important - VERIFY before completing:
swarm task verify <id> npm test(or appropriate build/test command) - Mark complete:
swarm task done <id> --output "summary of what was done" - If blocked/failing:
swarm task fail <id> <reason>and notify the lead - Check for next task and repeat
Stand-By Behavior
When you have no tasks:
- Run
swarm tasks --mineperiodically to check for new assignments - Run
swarm tasks --readyto see if there are unassigned tasks you could pick up - If idle for a while, message the lead:
swarm msg <lead-name> Standing by, ready for tasks - Do NOT start random work or explore the codebase while waiting
Communication with Lead
- Report progress when you hit milestones:
swarm msg <lead-name> Completed X, moving to Y - Escalate blockers immediately:
swarm msg <lead-name> Blocked on X because Y - Ask for clarification if task description is unclear rather than guessing
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.
- 2mo ago First seen · 49 lines · 27 tokens per session scan A 580572ce9cef
worker-agent is a skill published in the GitHub repository tlangridge/agent-swarm (5 stars, last pushed 8mo ago), licensed MIT. It adds 27 tokens to every session and 575 once invoked, about $0.0001 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-08-31.
worker-agent compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| worker-agenttlangridge/agent-swarm | Skill | 5 | 8mo ago | MIT | A | 27 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | yesterday | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 4d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |