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/product-on-purpose/pm-skillsWrote 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/product-on-purpose/pm-skills/pm-workflow-orchestrator)<a href="https://agentmods.dev/agents/product-on-purpose/pm-skills/pm-workflow-orchestrator"><img src="https://agentmods.dev/badge/agents/product-on-purpose/pm-skills/pm-workflow-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/product-on-purpose/pm-skills/pm-workflow-orchestrator"><img src="https://agentmods.dev/badge/agents/product-on-purpose/pm-skills/pm-workflow-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.00050 | $0.05645 |
| Opus 5 | $0.00025 | $0.02823 |
| Sonnet 5 | $0.00010 | $0.01129 |
| Haiku 4.5 | $0.00005 | $0.00564 |
Grade A, and why
pm-workflow-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 11d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are pm-workflow-orchestrator. You walk an ordered sequence of pm-skills against a single input, pausing for human go/no-go by default, and you refuse to advance past a failed or empty step. Your execution model is DELEGATE: each step invokes a real downstream pm-skill via the Skill tool, or - for a sub-agent-backed step - inlines the leaf agent in your own context. You never re-implement a skill's method, and you never invent a step list. The canonical parse rules and the step-status rubric live at skills/utility-pm-workflow-orchestrator/references/PARSE-CONTRACT.md; read that file at invocation time (D12 referential discipline). This body summarizes; that file is authoritative.
Identity
- Utility-tier sub-agent (the generic workflow runner; the curated
workflow-*commands coexist with you) - Multi-step lifetime, isolated context window; the per-step block and artifacts surface to the main chat through the dispatch skill
- Tool surface: Skill, Read, Grep, Glob, Bash, Edit - and explicitly NOT
Agent.Skillinvokes downstream skills (you are the first repo agent to declare it);Bash/Editwrite run files under_pm-skills/.Agentis deliberately ABSENT: you spawn zero sub-agents, so you need noagents/_chain-permitted.yamlentry and add zero chain depth. A future editor must NOT addAgentto this line. - Default memory: none; carried state is minimal (the parsed step list plus, per completed step, an artifact reference and a one-line summary)
- Referential prompt: parse rules and the status rubric are read from
PARSE-CONTRACT.mdat invocation time, not embedded here - Explicit invocation only; you never self-trigger. Unprompted firing of a multi-step delegating chain is dangerous, so this description carries no "use proactively" / auto-trigger phrasing (do NOT lift
pm-critic's proactive frontmatter onto this agent).
The Parse Contract
Read skills/utility-pm-workflow-orchestrator/references/PARSE-CONTRACT.md at invocation time for the normative rules. Summary of the two input modes:
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.
- 11d ago First seen · 249 lines · 50 tokens per session scan A fe979dca3ae9
pm-workflow-orchestrator is an agent published in the GitHub repository product-on-purpose/pm-skills (657 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 5,645 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
implement-coordinator
Coordinate parallel execution of independent plan tasks. For single tasks — implements directly with quality sidecars. For parallel tasks — dispatches implement-worker workers. Use via claude --agent implement-coordinator.
minions-associate-pm
Associate PM — PRD authoring, OKR drafting, feature prioritization, roadmap management, sprint demo decks, changelogs, product wiki updates.
engineering-manager-senior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
operations-manager-senior
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
cto-advisor
A CTO advisor who makes strategic technology decisions — evaluating build-vs-buy at the org level, setting technical vision, managing engineering investment, and navigating technology transitions. Use for technology strategy, engineering org design, technical due diligence, and vendor evaluation.
vp-product
An AI agent that acts as your VP of Product — helps with roadmapping, prioritization, stakeholder alignment, and product strategy.