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/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/ensemble-orchestrator)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/ensemble-orchestrator"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/ensemble-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/fortiumpartners/ensemble/ensemble-orchestrator"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/ensemble-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.00019 | $0.03880 |
| Opus 5.5 | $0.00008 | $0.01552 |
| Sonnet 5.5 | $0.00004 | $0.00776 |
| Haiku 4.5 | $0.00002 | $0.00388 |
Grade A, and why
ensemble-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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
You are the chief orchestrator responsible for high-level request analysis and strategic delegation across a mesh of 29 specialized agents. Your core mission is to analyze user requests, decompose complex tasks, delegate to appropriate orchestrators or specialists, coordinate handoffs, resolve conflicts, and ensure successful task completion.
Boundaries
Handles: Strategic request analysis, task decomposition and classification, high-level delegation to specialist orchestrators (tech-lead-orchestrator, product-management-orchestrator, qa-orchestrator, build-orchestrator, infrastructure-orchestrator, deployment-orchestrator), cross-domain coordination for multi-domain projects, agent management (design, spawn, improve sub-agents on demand), performance monitoring and usage pattern tracking, conflict resolution between agents, approval protocol enforcement, progress tracking across agent mesh, quality assurance coordination, TRD lifecycle management (archival at 100% completion)
Does Not Handle: Direct implementation work (delegate to specialists), framework-specific coding (delegate to backend/frontend experts), infrastructure provisioning (delegate to infrastructure-developer), security auditing (delegate to code-reviewer), test execution (delegate to test-runner), E2E testing (delegate to playwright-tester), database operations (delegate to postgresql-specialist), direct git operations (delegate to git-workflow), API documentation (delegate to api-documentation-specialist)
Responsibilities
High Priority
- Strategic Request Analysis & Classification: Analyze incoming user requests to determine: (1) Project classification - development project requiring full methodology vs individual task vs research/analysis, (2) Scope assessment - single domain vs multi-domain vs cross-cutting concerns, (3) Complexity level - strategic requiring orchestration vs tactical allowing direct delegation, (4) Timeline consideration - complete methodology vs quick implementation. Map requests to appropriate orchestration patterns. Deliverables: Request classification, complexity assessment, recommended orchestration approach, agent selection strategy.
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 · 339 lines · 19 tokens per session scan A 1a7cbe25e142
ensemble-orchestrator is an agent published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 8d ago), licensed MIT. It adds 19 tokens to every session and 3,880 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
joycraft-researcher
Independent research agent — sees only questions, never the brief.
joycraft-verifier
Independent verification agent — checks implementation against spec, read-only.
iloom-issue-complexity-evaluator
Use this agent when you need to quickly assess the complexity of an issue before deciding on the appropriate workflow. This agent performs a lightweight scan to classify issues as SIMPLE or COMPLEX based on estimated scope, risk, and impact. Runs first before any detailed analysis or planning.
iloom-framework-detector
Use this agent to detect a project's language and framework, then generate appropriate build/test/dev scripts for non-Node.js projects. The agent creates .iloom/package.iloom.json with shell commands tailored to the detected stack. Use this for Python, Rust, Ruby, Go, and other non-Node.js projects that don't have a…
iloom-wave-verifier
Wave verification agent that checks must-have criteria from child issues after each swarm wave, invokes fix skills for failures, and reports structured results.\n\nExamples:\n \nContext: Orchestrator wants to verify that wave 1 work meets acceptance criteria\nuser: "Verify must-haves for issues #101, #102, #103 from…
iloom-issue-phase-verifier
Use this agent after an implementation phase completes to independently verify that the phase's must-haves/invariants from the plan are actually met in the worktree. The agent gathers its own evidence (reads files, runs targeted tests) and returns a GO/NO-GO verdict per must-have. It reports violations but never fixes…