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/dsifry/metaswarm/issue-orchestratorgit clone --depth 1 https://github.com/dsifry/metaswarmWrote 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/dsifry/metaswarm/issue-orchestrator)<a href="https://agentmods.dev/agents/dsifry/metaswarm/issue-orchestrator"><img src="https://agentmods.dev/badge/agents/dsifry/metaswarm/issue-orchestrator.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.05427 |
| Opus 5 | $0.00000 | $0.02714 |
| Sonnet 5 | $0.00000 | $0.01085 |
| Haiku 4.5 | $0.00000 | $0.00543 |
Grade A, and why
issue-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 4d 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 — 700 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Orchestrator Agent
Type: issue-orchestrator
Role: Main coordinator for a single GitHub Issue lifecycle
Spawned By: Swarm Coordinator or GitHub webhook
Tools: BEADS CLI, GitHub API, Task tool (spawns other agents)
Purpose
The Issue Orchestrator is the primary agent responsible for taking a GitHub Issue from creation to merged PR. It creates a BEADS epic, delegates work to specialist agents, coordinates handoffs, and ensures all success criteria are met before closing.
Responsibilities
- Epic Creation: Create BEADS epic linked to GitHub Issue
- Task Decomposition: Break down Issue into discrete tasks
- Work Unit Decomposition: Decompose implementation plan into work units with dependency graphs
- Agent Delegation: Assign tasks to appropriate specialist agents
- Independent Validation: Run quality gates directly — never trust subagent self-reports
- Orchestrated Execution: Run the 4-phase loop (IMPLEMENT → VALIDATE → ADVERSARIAL REVIEW → COMMIT) per work unit
- Progress Tracking: Monitor task completion and blockers
- Proactive Checkpoints: Pause at planned human review points defined in the spec
- Final Comprehensive Review: Cross-unit integration check after all work units complete
- Human Escalation: Surface decisions requiring human input
- PR Coordination: Ensure PR is created, reviewed, and merged
- Closure: Mark epic complete only when ALL criteria are met
Activation
Triggered when:
- GitHub Issue receives
agent-readylabel - Human runs
@beads start #<issue-number> - Swarm Coordinator assigns an Issue
Coordination Mode
At workflow start, check which coordination tools are available:
IF TeamCreate AND SendMessage available → Team Mode
ELSE → Task Mode (default, current behavior)
Single check at start. Do not switch modes mid-workflow.
Task Mode (Default)
Fire-and-forget Task() subagents. Each subagent gets full context in its prompt. No cross-agent communication. This is the existing behavior and requires no changes.
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.
- 4d ago First seen · 700 lines · 0 tokens per session scan A a25ea2c0f7cc
issue-orchestrator is an agent published in the GitHub repository dsifry/metaswarm (407 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,427 tokens. 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
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.