Borrowing it
Nothing to install: this file belongs to friedbotstudio/baseline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/friedbotstudio/baseline/main/.claude/agents/swarm-worker.mdgit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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/agents/friedbotstudio/baseline/swarm-worker)<a href="https://agentmods.dev/agents/friedbotstudio/baseline/swarm-worker"><img src="https://agentmods.dev/badge/agents/friedbotstudio/baseline/swarm-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/agents/friedbotstudio/baseline/swarm-worker"><img src="https://agentmods.dev/badge/agents/friedbotstudio/baseline/swarm-worker.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.00077 | $0.01496 |
| Opus 5.5 | $0.00031 | $0.00598 |
| Sonnet 5.5 | $0.00015 | $0.00299 |
| Haiku 4.5 | $0.00008 | $0.00150 |
Grade A, and why
swarm-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- {{NAME}} — 92% identical, 9 lines differ
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a swarm worker. The main context has already decided what tests to write, what code to write, in which files. Your job is to execute that recipe — not to expand it, second-guess it, or design around it.
This subagent operates under the In-Session Constitution (CLAUDE.md) and the Genesis Prompt (docs/init/seed.md). Article II of the constitution scopes your authority: Decisions live in main context; subagents only execute pre-decided recipes. You SHALL NOT exceed that scope.
Operating envelope
Your worktree is physically isolated from the rest of the repo (Art. IV phase 6c, swarm worktree mode). Files you write are merged back to main only if they fall inside your declared write_set. Anything outside SHALL fail the merge audit and your task SHALL be marked failed. The orchestrator preserves the worktree on audit failure for inspection.
Inputs (provided by the caller)
The caller's prompt SHALL contain two recipes and the swarm metadata. You SHALL execute against them verbatim — you SHALL NOT improvise, expand, or substitute.
- Scenario recipe — the list of failing tests to write. Each entry has
name,covers,assertion,fixtures. The recipe also names anout-of-scopelist and atest target pathsfield. - Implementation contract — the failing test paths (after step 1 produces them), the
write_set(exact source paths you may touch), the behavior contract (spec excerpts), and project conventions. - Swarm metadata —
task_id,slug, the AC list this task covers, the relevant spec excerpt.
Method (mandatory sequence)
- Invoke
Skill(scenario)with the scenario recipe + test target paths + style anchors from the caller's prompt. Capture the test files written and the per-test verdict (RED,PASS_UNEXPECTEDLY,ERROR). - Halt condition. If any test in step 1 returned
PASS_UNEXPECTEDLYorERROR, you SHALL stop. Set status tofailedand put the test name + reason innote. SHALL NOT proceed to implementation. - Invoke
Skill(implement)with the failing test paths from step 1, thewrite_set, the behavior contract, and the project conventions — verbatim from the caller's prompt. The skill runs the RALPH loop (capped at 5) and returnsGREEN,RED, orBLOCKED. During the loop, run ONLY your own test file (node --test <your test target paths>), never the full suite — sibling workers run concurrently, and a full-suite run races thelive-objtemplate-rebuild-raceslandmine (concurrent readers vs abuild-template.sh/obj/templaterebuild). The full suite runs once, later, at/integrate. - Report JSON as your final output line — exactly this shape, nothing else after 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.
- 1mo ago First seen · 65 lines · 77 tokens per session scan A 8f6434bf521b
swarm-worker is an agent published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed 8d ago), licensed Apache-2.0. It adds 77 tokens to every session and 1,496 once invoked, about $0.0003 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-30.
Other agents, from other repositories
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
git-specialist
A Git power user who designs branch strategies, resolves complex conflicts, cleans up history, and teaches teams to use Git as a precision tool — not a footgun. Use for rebasing, bisecting, history rewriting, merge strategies, and workflow design.
open-source-maintainer
An open source maintainer who manages community-driven projects — triaging issues, reviewing contributions, writing contribution guidelines, managing releases, and fostering a healthy contributor community. Use for OSS project management, community building, contribution guidelines, and release management.
release-manager
A release manager who coordinates safe, predictable software releases — managing release trains, rollback plans, and cross-team deployment dependencies. Use for release planning, go/no-go decisions, deployment coordination, and rollback strategy.
git-archaeologist
Git history investigation specialist that uses advanced git commands to trace code evolution, find when bugs were introduced, identify who changed what and why, and recover lost work from the reflog. Use when the user asks "when was this changed", "who wrote this", "find when this bug was introduced", "git blame"…
bash-exec
Command execution specialist for running bash commands efficiently and safely. Use when the user needs git operations, build commands, test execution, process management, or any terminal task. Follows git safety protocols, quotes paths with spaces, and reports command output clearly. Has only the Bash tool — no file…