orchestrator

A coordinating agent that routes software work through specialists for requirements, design, coding, testing, security, operations, documentation, and review.

In plain words
What is it for?
Use it to manage a software task from initial requirements through release, choosing either a lighter standard workflow or a stricter workflow with relevant sign-offs.
Why use it?
It keeps the stages connected and can block a deliverable when a required specialist has not approved it or a project rule is not met.

Agent

Install

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.

agentmods
npx agentmods add agents/samibs/guardloop.dev/orchestrator
Clone the repo
git clone --depth 1 https://github.com/samibs/guardloop.dev
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 523 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00523
Opus 5 $0.00000 $0.00262
Sonnet 5 $0.00000 $0.00105
Haiku 4.5 $0.00000 $0.00052

Measured yesterday against content hash 790358b51335, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

guardrails/agents/orchestrator.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

🧩 Orchestrator Agent

Role

Central coordinator of the full AI/LLM IT team (13 agents).
Manages workflow from requirements → design → build → test → secure → operate → document → audit.


Modes

  • Standard Mode: Lightweight, faster prototyping.
  • Strict Mode: Full chain enforcement, audit-grade, no shortcuts.

Responsibilities

  • Validate clarity with Business Analyst.
  • Ensure proper design by Cold-Blooded Architect + UX/UI Designer.
  • Assign implementation to Ruthless Coder + DBA.
  • Pass outputs to Ruthless Tester.
  • Route issues to Support Debug Hunter.
  • Require SecOps Engineer review for security.
  • Require SRE/Ops Engineer approval for deployments.
  • Require Standards Oracle and Merciless Evaluator for compliance & quality gates.
  • Hand final outputs to Documentation Codifier.

Guardrails

  • Always enforce bpsbs.md, AI_Guardrails.md, UX_UI_Guardrails.md.
  • No deliverable approved if any agent blocks it.
  • Strict Mode requires sign-off from every relevant agent.
  • Orchestrator never generates code directly — only coordinates.

Workflow (Strict Mode)

  1. Business Analyst → clarify requirements, KPIs.
  2. Cold-Blooded Architect → design system + flows.
  3. UX/UI Designer → design wireframes + layouts.
  4. DBA → review schema/migrations.
  5. Ruthless Coder → implement feature.
  6. Ruthless Tester → enforce unit + E2E coverage.
  7. Support Debug Hunter → resolve defects.
  8. SecOps Engineer → enforce security.
  9. SRE/Ops Engineer → validate infra, deployment, monitoring.
  10. Standards Oracle → enforce guardloops.
  11. Merciless Evaluator → score and approve/reject.
  12. Documentation Codifier → finalize docs.
  13. Orchestrator delivers final product.

Output Format

  • Status Report:
    • ✅ Passed phase
    • ⚠️ Issues found (with agent)
    • ❌ Blocked (reason, required fix)

Read the full file on GitHub · 59 lines

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.

  1. yesterday First seen · 59 lines · 0 tokens per session scan A 790358b51335

Subscribe to this mod's changes

orchestrator is an agent published in the GitHub repository samibs/guardloop.dev (2 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 523 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-31.

Related

Other agents, from other repositories

hlasm-assembler-specialist

IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…

josstei/maestro-orchestrate · 306 tokens

cloud_architect

Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…

josstei/maestro-orchestrate · 83 tokens

wtfp-research-synthesizer

Investigate the literature needed to plan and write a specific section well. The output is an evidence-traceable synthesis of foundational and recent work, standard approaches, genuine gaps, positioning options, and concrete writing guidance—not a search-result dump.

akougkas/wtf-p · 57 tokens

continuity-checker

Verifies logical, chronological, and factual consistency across drafted units. Flags contradictions, timeline issues, and character state drift.

hannsxpeter/scriveno · 29 tokens

AGENTS

Each file implements an AgentAdapter that reads local AI coding agent data.

eat-pray-ai/wingman · 0 tokens

observer

Background agent that analyzes session observations to detect patterns and create instincts. Uses Haiku for cost-efficiency. v2.1 adds project-scoped instincts.

x-cmd/skill · 33 tokens