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 skills add stefanoskarakasis/Product-Marketing-Skills --skill workflow-orchestratorgit clone --depth 1 https://github.com/stefanoskarakasis/Product-Marketing-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/skills/stefanoskarakasis/product-marketing-skills/workflow-orchestrator)<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/workflow-orchestrator"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/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/skills/stefanoskarakasis/product-marketing-skills/workflow-orchestrator"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/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.00105 | $0.04473 |
| Opus 5.5 | $0.00042 | $0.01789 |
| Sonnet 5.5 | $0.00021 | $0.00895 |
| Haiku 4.5 | $0.00011 | $0.00447 |
Grade A, and why
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 13d 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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PMM Workflow Orchestrator
Chains your PMM skills into complete end-to-end programs. Manages state across skills, verifies coherence between outputs, writes back to brain, and produces one master program document the team can act from.
Not a shortcut for running one skill. A program manager for multi-skill PMM work where consistency across outputs — positioning, competitive, GTM, stakeholder — matters as much as each individual output.
Trigger
- When: Any request for a multi-step PMM program spanning two or more skills, or any named workflow type below.
- Not for: Single-skill tasks — route directly to the relevant skill instead:
go-to-market-strategyfor tier + brief only,gtm-motionsfor motion selection only,positioning-messagingfor positioning work only,pre-mortemfor risk analysis only,retrofor post-launch review only. - Example prompts:
- "Run a full launch workflow for our analytics dashboard"
- "We're doing a positioning refresh — orchestrate the full program"
- "Run our quarterly PMM cycle"
- "New market entry into healthcare — full program"
- "I just joined as PMM — audit the current state"
- "Run a competitive intelligence program on our top 3 competitors"
Inputs
- Args: Workflow type (named or described) + initiative context. See Commands for supported workflow types. Free-form description also accepted — orchestrator will infer the closest workflow and confirm before running.
- Defaults: If workflow type is ambiguous, ask before starting. Never infer and execute silently on a multi-skill program.
- Context keys:
/foundation/brain.md— required. All sections.- Brain contract:
- Reads: Sections 1–6 — checks completeness and staleness before routing.
- Writes: Section 3 (after positioning or alternatives refresh, via
alternatives-maporpositioning-messaging), Section 6 (after new proof points confirmed, viaproof-points). - Never writes to: Section 1, Section 2, Section 4, Section 5 (those require
dedicated skills:
product-marketing-context). The orchestrator itself never writes brain content directly in any section — every write above is performed by the named downstream skill and only confirmed here.
- Staleness thresholds:
- Section 3 (Alternatives & Positioning) > 6 months → flag for refresh before any launch workflow.
- Section 6 (Proof Points) containing unresolved
[NEEDS PROOF]/[NEEDS APPROVAL]entries → flag for aproof-pointsAudit pass before any workflow that cites claims externally (sales enablement, launch brief).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago Changed · -2 lines · -12 tokens per session d602ac940320
- 19d ago Changed · +1 lines a0d9b0de350d
- 20d ago Changed · +3 lines d22bb97154bb
- 21d ago Changed · +8 lines 363d739a517f
- 22d ago Changed · -3 lines ff2ca85e0e73
- 1mo ago Changed · +16 lines f34ee10c58bb
- 1mo ago Changed · +2 lines 0e28bd192145
- 2mo ago First seen · 425 lines · 117 tokens per session scan A a2680ceae962
workflow-orchestrator is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (8 stars, last pushed yesterday), licensed MIT. It adds 105 tokens to every session and 4,473 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
sprint-plan
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
review-resume
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
job-stories
Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.
stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
brainstorm-ideas-existing
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.