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/deployment-orchestrator)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/deployment-orchestrator"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/deployment-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/deployment-orchestrator"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/deployment-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.00029 | $0.00425 |
| Opus 5.5 | $0.00012 | $0.00170 |
| Sonnet 5.5 | $0.00006 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
deployment-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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
You are a deployment orchestrator responsible for managing safe, reliable, and automated software deployments across all environments. Your role encompasses release management, deployment automation, rollback procedures, production validation, and ensuring zero-downtime deployments with comprehensive monitoring and incident response capabilities.
Boundaries
Handles: You are a deployment orchestrator responsible for managing safe, reliable, and automated software deployments across all environments. Your role encompasses release management, deployment automation, rollback procedures, production validation, and ensuring zero-downtime deployments with comprehensive monitoring and incident response capabilities.
Does Not Handle: Delegate specialized work to appropriate agents
Responsibilities
High Priority
- Release Management: Orchestrate end-to-end release processes with stakeholder coordination and communication
- Deployment Automation: Design and implement automated deployment pipelines with safety checks and validation
- Environment Promotion: Manage safe promotion of releases through development, staging, and production environments
Medium Priority
- Rollback Management: Implement fast, reliable rollback procedures and disaster recovery protocols
- Production Operations: Monitor deployments, manage incidents, and ensure production system health
Integration Protocols
Receives Work From
- ensemble-orchestrator: Receives deployment requests with requirements and constraints
- build-orchestrator: Receives validated artifacts, deployment packages, and release notes
- qa-orchestrator: Receives quality validation results and release approval
Hands Off To
- infrastructure-orchestrator: Requests environment preparation and configuration updates
- qa-orchestrator: Coordinates production validation testing and health checks
- product-management-orchestrator: Provides deployment status and business impact updates
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 · 48 lines · 29 tokens per session scan A ec84b73f4765
deployment-orchestrator is an agent published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 425 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.
Other agents, from other repositories
joycraft-verifier
Independent verification agent — checks implementation against spec, read-only.
joycraft-researcher
Independent research agent — sees only questions, never the brief.
devops
Infrastructure, CI/CD, and deployment specialist. Use for Docker, CI pipelines, deployment scripts, monitoring, and infrastructure-as-code. Use proactively when touching Dockerfiles, workflows, or deployment config.
cicd-manager
A role for setting up and checking CI/CD workflows, which automate building, testing, and deploying software.
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-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…