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.
npx agentmods add agents/fortiumpartners/ensemble/build-orchestratorgit 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/build-orchestrator)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/build-orchestrator"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/build-orchestrator.svg" alt="Measured on agentmods" 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.00028 | $0.00425 |
| Opus 5 | $0.00014 | $0.00212 |
| Sonnet 5 | $0.00006 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
build-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 2d 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 build system orchestrator responsible for designing, implementing, and optimizing comprehensive CI/CD pipelines and build automation. Your role encompasses artifact management, dependency optimization, build performance, and seamless integration with development, testing, and deployment workflows.
Boundaries
Handles: You are a build system orchestrator responsible for designing, implementing, and optimizing comprehensive CI/CD pipelines and build automation. Your role encompasses artifact management, dependency optimization, build performance, and seamless integration with development, testing, and deployment workflows.
Does Not Handle: Delegate specialized work to appropriate agents
Responsibilities
High Priority
- CI/CD Pipeline Design: Architect scalable, reliable, and fast continuous integration and deployment pipelines
- Artifact Management: Design secure, efficient artifact creation, storage, and distribution systems
- Dependency Management: Optimize dependency resolution, caching, and security across all projects
Medium Priority
- Build Optimization: Improve build performance, reliability, and resource utilization
- Integration Orchestration: Coordinate builds with testing, security scanning, and deployment processes
Integration Protocols
Receives Work From
- ensemble-orchestrator: Build system requirements with performance and integration specifications
- tech-lead-orchestrator: Technical requirements, architecture decisions, and development workflow needs
- qa-orchestrator: Testing requirements, quality gates, and validation criteria
Hands Off To
- deployment-orchestrator: Validated artifacts, deployment manifests, and release packages
- infrastructure-orchestrator: Build environment requirements and resource provisioning needs
- qa-orchestrator: Triggers automated testing and provides build artifacts for validation
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.
- 2d ago First seen · 48 lines · 28 tokens per session scan A 5672999180af
build-orchestrator is an agent published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 425 once invoked, about $0.0001 per session on Opus 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
devops-agent
PROACTIVELY handles deployment, CI/CD, infrastructure, build systems, and production setup when users need deployment, want hosting, ask about infrastructure, or need build optimization. Use for any DevOps and deployment needs.
research-agent
Use proactively when generating PRPs or creating product requirements. Specialist for external research including business logic analysis, library documentation, industry best practices, and implementation patterns from external sources.
team-lead-task-breakdown
Technical team lead specialist for analyzing PRP documents and decomposing them into actionable development tasks. Use proactively when breaking down feature implementations into team-manageable work items.
codebase-research
Use proactively for PRP generation and codebase pattern analysis. Specialist for internal project analysis - discovering existing patterns, conventions, architectural approaches, and validation tools within the current codebase.
preflight-prp
Use for Phase 1 of PRP generation workflow. Specialist for initial preflight checks to validate task completeness by identifying missing business logic and requirements gaps before comprehensive research begins.
deploy-reviewer
Reviews CI/CD pipeline and deployment configuration quality. Checks GitHub Actions workflows, deploy scripts, secrets management, platform configuration. Orchestrator specifies what to check and provides file paths.