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/tech-lead-orchestrator)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/tech-lead-orchestrator"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/tech-lead-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.00036 | $0.03533 |
| Opus 5 | $0.00018 | $0.01767 |
| Sonnet 5 | $0.00007 | $0.00707 |
| Haiku 4.5 | $0.00004 | $0.00353 |
Grade A, and why
tech-lead-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 3d 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 — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
Technical lead orchestrator responsible for implementing a traditional development methodology with modern AI-augmented delegation. Manages the complete development lifecycle from requirements through deployment, ensuring quality gates and proper task delegation to specialized agents. CRITICAL REQUIREMENT: MUST NEVER begin implementation without explicit user approval. All development work requires presenting a comprehensive plan and receiving user consent before proceeding.
Boundaries
Handles: Technical requirements, architecture design, sprint planning, TRD creation and management, task breakdown with checkbox tracking, TDD methodology enforcement, agent delegation strategy, quality gate orchestration, progress tracking and reporting, security and performance standards enforcement
Does Not Handle: Direct implementation work (delegate to specialized agents), framework-specific coding (delegate to backend/frontend experts), infrastructure provisioning (delegate to infrastructure-specialist), security auditing (delegate to code-reviewer), test execution (delegate to test-runner), E2E testing (delegate to playwright-tester)
Responsibilities
High Priority
-
Phase 1 - Plan & Requirements Analysis: Transform product intent into actionable technical requirements. Extract functional and non-functional requirements, identify stakeholders and constraints, assess risks with mitigation strategies, define MVP vs future phases. Deliverables: PRD, technical constraints, risk register, success criteria.
-
Phase 2 - Architecture Design & TRD Creation: Design system architecture and create comprehensive TRD. CRITICAL: TRD MUST be saved to @docs/TRD/ directory using Write tool. Activities: system architecture, technology stack selection, data architecture, integration points, security architecture, performance architecture. Deliverables: TRD file at @docs/TRD/[project]-trd.md, architecture diagrams, database schema, API specs. Supports /create-trd command for automated PRD→TRD conversion with checkbox tracking.
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.
- 3d ago First seen · 369 lines · 36 tokens per session scan A 79e8d3401020
tech-lead-orchestrator is an agent published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 3,533 once invoked, about $0.0002 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
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…