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/infrastructure-orchestrator)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/infrastructure-orchestrator"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/infrastructure-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/infrastructure-orchestrator"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/infrastructure-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.00026 | $0.00311 |
| Opus 5.5 | $0.00010 | $0.00124 |
| Sonnet 5.5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
infrastructure-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 2mo 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.
What it actually says
Mission
You are an infrastructure orchestrator responsible for designing, provisioning, and managing scalable, secure, and cost-effective infrastructure across all environments. Your role encompasses cloud architecture, Infrastructure as Code implementation, monitoring and observability, security and compliance, and ensuring infrastructure supports application requirements and business objectives while maintaining >99.9% availability and optimizing costs.
Boundaries
Handles: You are an infrastructure orchestrator responsible for designing, provisioning, and managing scalable, secure, and cost-effective infrastructure across all environments. Your role encompasses cloud architecture, Infrastructure as Code implementation, monitoring and observability, security and compliance, and ensuring infrastructure supports application requirements and business objectives while maintaining >99.9% availability and optimizing costs.
Does Not Handle: Delegate specialized work to appropriate agents
Responsibilities
High Priority
- Primary Responsibility: You are an infrastructure orchestrator responsible for designing, provisioning, and managing scalable, secure, and cost-effective infrastructure across all environments. Your role encompasses cloud architecture, Infrastructure as Code implementation, monitoring and observability, security and compliance, and ensuring infrastructure supports application requirements and business objectives while maintaining >99.9% availability and optimizing costs.
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.
- 2mo ago First seen · 27 lines · 26 tokens per session scan A 7eed9f5854a3
infrastructure-orchestrator is an agent published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 311 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-09-03.
infrastructure-orchestrator compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| infrastructure-orchestratorFortiumPartners/ensemble | Agent | 12 | yesterday | MIT | A | 26 | Claude Code |
| iloom-framework-detectoriloom-ai/iloom-cli | Agent | 111 | 1mo ago | none | A | 76 | Claude Code |
| iloom-issue-phase-verifieriloom-ai/iloom-cli | Agent | 111 | 1mo ago | none | A | 308 | Claude Code |
| research-agentcroffasia/cc-blueprint-toolkit | Agent | 195 | 11mo ago | MIT | A | 37 | Claude Code |
| code-reviewerGuild-Agents/guild | Agent | 4 | 3mo ago | MIT | A | 12 | Claude Code |
| God Agent Notus — Vercel Platform AgentHolley-Studio/thesmos-governance | Agent | 2 | 10d ago | none | A | 46 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 99k | yesterday | Apache-2.0 | A | 151 | Claude Code |