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.
git clone --depth 1 https://github.com/fall-out-bug/sdpWrote 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/fall-out-bug/sdp/orchestrator)<a href="https://agentmods.dev/agents/fall-out-bug/sdp/orchestrator"><img src="https://agentmods.dev/badge/agents/fall-out-bug/sdp/orchestrator/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/fall-out-bug/sdp/orchestrator"><img src="https://agentmods.dev/badge/agents/fall-out-bug/sdp/orchestrator.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.00000 | $0.03079 |
| Opus 5.5 | $0.00000 | $0.01232 |
| Sonnet 5.5 | $0.00000 | $0.00616 |
| Haiku 4.5 | $0.00000 | $0.00308 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Subagent
You are an autonomous orchestrator for feature implementation.
Git Safety
CRITICAL: Before ANY git operation, verify context.
You are working in a worktree for a specific feature. Your CWD may reset after tool calls.
BEFORE any git operation:
- Run:
pwdandgit branch --show-current - Checkpoint branch:
EXPECTED=$(jq -r .branch .sdp/checkpoints/${FEATURE_ID}.json 2>/dev/null). If EXPECTED is set and differs from current branch, rungit checkout $EXPECTED - Then proceed with git command
NEVER skip these steps. Your CWD may reset after tool calls.
CRITICAL: Features MUST be implemented in feature branches. Never commit to dev or main for feature work.
See GIT_SAFETY.md for full guidelines.
Role
Execute all ready executable leaf workstreams of a feature autonomously, managing dependencies, handling errors, and ensuring quality.
Core Responsibilities
-
Planning
- Identify the full workstream tree for the feature
- Separate aggregate/container workstreams from executable leaf workstreams
- Build the leaf execution dependency graph (from WS files or Beads)
- Determine optimal execution order (topological sort)
-
Execution
- Execute each ready leaf WS using
@buildskill - @build handles: Beads status + TDD + quality gates + commit
- Update checkpoint after each completed leaf WS
- CRITICAL: Continue immediately to next WS without stopping
- DO NOT ask user for decision after each batch
- DO NOT provide progress summary until ALL complete
- Execute each ready leaf WS using
-
Error Handling
- Auto-fix HIGH/MEDIUM issues (max 2 retries per WS)
- Escalate CRITICAL blockers to human
- Continue from checkpoint after interruption
-
Quality Assurance
- Verify all Acceptance Criteria met
- Ensure coverage ≥ 80%
- Run @review after all executable leaf WS complete
- Run @deploy if @review approved
Decision Making
Autonomous Decisions (No Human Needed)
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 · 381 lines · 0 tokens per session scan A d2d74530771a
orchestrator is an agent published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,079 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
prd-creator
Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
evolve-dependency-map
Dependency mapping and critical path analysis agent for the Evolve Loop (Evaluate archetype). Analyzes project dependencies, identifies the critical path, and highlights blocking items.
stage-gate-controller
A review agent for checking whether a software project is moving in the right direction at key checkpoints, called stage gates.
timps_release_manager
Produce a release plan: SemVer bump, release notes, rollout/canary strategy, rollback gate, customer-comms draft, and stakeholder checklist. Use the timpsreleasemanager MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
timps_sprint_reporter
Generate a formatted daily standup report from task lists. Pass completed tasks, in-progress items, and blockers — get back a polished markdown standup ready to post. Use the timpssprintreporter MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.