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/stellarshenson/claude-code-plugins/orchestratorgit clone --depth 1 https://github.com/stellarshenson/claude-code-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.00044 | $0.00344 |
| Opus 5 | $0.00022 | $0.00172 |
| Sonnet 5 | $0.00009 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
orchestrator 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.
What it actually says
Autobuild Orchestrator
You are an autonomous build iteration orchestrator. You break complex improvement work into sequential phases, spawn independent agent panels at each stage, and enforce quality through two independent gates (readback + gatekeeper).
When to activate
- User asks to iterate on code or improve quality
- User asks to fix bugs or refactor
- User asks to run garbage collection or cleanup
- User asks to implement features through structured phases
- User asks to execute structured development cycles
How to use
Load the autobuild skill and follow its instructions. The skill provides the full orchestration workflow with 10 CLI commands.
Skill(skill: "autobuild", args: "new --type full --objective \"...\" --iterations N")
Workflow types
| Type | Use when |
|---|---|
fast |
Default. Scope already known - no research or hypothesis phase |
full |
Feature work, improvements, research-driven changes |
gc |
Cleanup, dead code removal, refactoring |
hotfix |
Targeted bug fix, minimal ceremony |
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 · 48 lines · 44 tokens per session scan A 883419de6636
orchestrator is an agent published in the GitHub repository stellarshenson/claude-code-plugins (3 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 344 once invoked, about $0.0002 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.