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 RudyCity/superagent --skill master-agent-orchestrationgit clone --depth 1 https://github.com/RudyCity/superagentWrote 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/rudycity/superagent/master-agent-orchestration)<a href="https://agentmods.dev/skills/rudycity/superagent/master-agent-orchestration"><img src="https://agentmods.dev/badge/skills/rudycity/superagent/master-agent-orchestration/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/rudycity/superagent/master-agent-orchestration"><img src="https://agentmods.dev/badge/skills/rudycity/superagent/master-agent-orchestration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 64 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00028 | $0.01507 |
| Opus 5 | $0.00014 | $0.00754 |
| Sonnet 5 | $0.00006 | $0.00301 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
Master Agent Orchestration 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 5d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Master Agent Orchestration
Overview
The Master Agent (depth 0) acts as the central orchestrator and coordinator. It does not modify code directly. Instead, it creates isolated worktrees, delegates feature-level development tasks to Superagents (depth 1), monitors their progress, and merges the results back into the main branch.
Master Agent (depth 0)
/ | \
Superagent Superagent Superagent (depth 1)
/ \ | / \
Subagent Subagent Subagent Subagent Subagent (depth 2)
The Orchestration Tools
| Tool Name | Purpose | Key Parameters | Typical Usage Pattern |
|---|---|---|---|
invoke_superagent |
Spawns a Superagent on a new git branch & isolated worktree. | role, task, branch, wait (optional) |
invoke_superagent({ role: "ui-dev", task: "Build login screen", branch: "feat/login", wait: false }) |
await_superagents |
Waits for all running Superagents to finish their tasks. | timeoutSeconds (optional) |
await_superagents({ timeoutSeconds: 600 }) |
merge_superagents |
Merges completed Superagent branches with conflict resolution. | cleanupWorktrees (optional) |
merge_superagents({ cleanupWorktrees: true }) |
manage_superagents |
Lists instances, views logs/reports, or terminates agents. | action (list/logs/report/kill/kill_all), superagentIds |
manage_superagents({ action: "list" }) |
git_worktree |
Manages git worktree configurations manually. | action, branch, path |
git_worktree({ action: "list" }) |
Core Workflow
1. Planning and Delegation
- Split complex requests into independent, parallelizable feature tasks.
- Assign each feature task a descriptive role, a task prompt, and a unique branch name (e.g.
feat/database-logger). - Spawn them concurrently using
invoke_superagentwithwait: false.
2. Monitoring Progress
- Use
manage_superagentswithaction: "list"to check the status of all spawned instances. - If a Superagent is taking long or you suspect issues, fetch active output logs using
manage_superagentswithaction: "logs"and the target ID. - Use
await_superagentsto pause execution until all delegated tasks finish.
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.
- 5d ago Changed · +4 lines d9d873896631
- 6d ago First seen · 106 lines · 28 tokens per session scan A 894e5eba03bc
Master Agent Orchestration is a skill published in the GitHub repository RudyCity/superagent (21 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 1,507 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.