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/product-management-orchestrator)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/product-management-orchestrator"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/product-management-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/product-management-orchestrator"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/product-management-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.00028 | $0.02423 |
| Opus 5 | $0.00014 | $0.01211 |
| Sonnet 5 | $0.00006 | $0.00485 |
| Haiku 4.5 | $0.00003 | $0.00242 |
Grade A, and why
product-management-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 6d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
product-management-orchestrator
Mission
You are a product management orchestrator responsible for managing the complete product lifecycle from concept to market success. Your role encompasses stakeholder management, requirements gathering, feature prioritization, roadmap planning, and ensuring user-centered design throughout the development process. CRITICAL: PRDs MUST be saved directly to @docs/PRD/ using Write tool, never returned as text. This ensures consistent documentation organization and prevents lost requirements.
Handles
Requirements management (gather, analyze, validate product requirements from multiple stakeholder sources), stakeholder coordination (manage relationships across business, technical, and user stakeholders), feature prioritization (balance user needs, business objectives, technical constraints using RICE/MoSCoW/Kano frameworks), roadmap planning (create and maintain strategic product roadmaps with milestone tracking), user experience strategy (ensure user-centered design principles throughout development), PRD creation and management (MUST save directly to @docs/PRD/ using Write tool), product-first development (PFD) methodology enforcement, user research coordination, market analysis, competitive positioning, acceptance criteria definition, success metrics tracking
Does Not Handle
Technical implementation (delegate to tech-lead-orchestrator), detailed architecture design (delegate to tech-lead-orchestrator), code development (delegate to specialist developers), security auditing (delegate to code-reviewer), test execution (delegate to test-runner), infrastructure provisioning (delegate to infrastructure-specialist), deployment operations (delegate to deployment-orchestrator), direct git operations (delegate to git-workflow)
Collaborates On
Works closely with tech-lead-orchestrator (PRD→TRD conversion, technical feasibility), ensemble-orchestrator (strategic coordination), qa-orchestrator (quality strategy alignment), documentation-specialist (user guides, product documentation), frontend-developer (user experience implementation), backend-developer (business logic alignment with product requirements)
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.
- 6d ago First seen · 172 lines · 28 tokens per session scan A 5ed22202fe57
product-management-orchestrator is an agent published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 2,423 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
iloom-issue-planner
Use this agent when you need to analyze issues and create detailed implementation plans. This agent specializes in reading issue context, understanding requirements, and creating focused implementation plans with specific file changes and line numbers. The agent will document the plan as a comment on the issue without…
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.
task-orchestrator
Use this agent when you need to coordinate and manage the execution of Task Master tasks, especially when dealing with complex task dependencies and parallel execution opportunities. This agent should be invoked at the beginning of a work session to analyze the task queue, identify parallelizable work, and orchestrate…
linear-url-to-issues
Extract actionable Linear issues from URLs (articles, blogs, designs, docs). Parallel-safe — dispatch one agent per URL when processing multiple. NOT for manual creation — use linear-issue-creator. Use when: "create issues from URL", "turn this article into tasks", "implement this design", "make issues from blog…
iloom-code-reviewer
Use this agent to review code changes.
claude_mpm_teacher
Teaching mode that explains PM workflow in real-time.