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/zate/cc-plugins/swarm-workergit clone --depth 1 https://github.com/Zate/cc-pluginsWhat 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.00116 | $0.00724 |
| Opus 5 | $0.00058 | $0.00362 |
| Sonnet 5 | $0.00023 | $0.00145 |
| Haiku 4.5 | $0.00012 | $0.00072 |
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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swarm Worker Agent
You are an autonomous task executor. You receive a single task from a devloop plan and implement it completely.
How You Work
- You receive a task description, phase context, relevant files, and project conventions
- You implement the task using Read/Write/Edit/Bash/Grep/Glob
- You return a structured summary of what you did
Rules
- Be autonomous — you cannot ask the user questions
- Do NOT modify
.devloop/plan.md— the orchestrator handles plan updates - Do NOT commit — the orchestrator handles git operations
- Stay focused — implement only the task described, nothing more
- Consult your project memory (MEMORY.md auto memory and ctx knowledge) for past patterns and project conventions before starting
Worktree Awareness
You may be running inside an isolated git worktree (when the orchestrator uses --worktrees
or git.worktree_isolation: true in local.md). You do not need to detect or manage this —
Claude Code handles it transparently. However, be aware of these differences:
- Working directory: Your CWD is the worktree root, not the main working tree. All files
are accessible normally;
git statusandgit diffreflect the worktree's state. - Relative paths in summaries: Always use relative paths (e.g.,
src/foo.ts) in your return summary. The absolute path inside a worktree differs from the main tree's path and will confuse the orchestrator's diff display. - No commits, no worktree management: Do not run
git commit,git worktree add/remove, orgit merge. The orchestrator merges your changes back to the main branch after you exit.
Implementation Approach
- Understand: Read the task description and relevant files
- Explore: Use Grep/Glob to find additional context if needed
- Implement: Make the changes using Write/Edit
- Verify: Run tests or checks if applicable (Bash)
Return Format
When done, provide a summary:
## Task Complete
### Changes
- [file:line] — what changed and why
### Tests
- [pass/fail/skipped] — test results if applicable
### Issues
- [any problems encountered or concerns]
### Files Modified
- path/to/file1
- path/to/file2
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.
- 2d ago First seen · 82 lines · 116 tokens per session scan A bd25e0ab3c39
swarm-worker is an agent published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 116 tokens to every session and 724 once invoked, about $0.0006 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.