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/marfoerst/the-pragmatic-pmWrote 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/marfoerst/the-pragmatic-pm/pm-ops-facilitator)<a href="https://agentmods.dev/agents/marfoerst/the-pragmatic-pm/pm-ops-facilitator"><img src="https://agentmods.dev/badge/agents/marfoerst/the-pragmatic-pm/pm-ops-facilitator/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/marfoerst/the-pragmatic-pm/pm-ops-facilitator"><img src="https://agentmods.dev/badge/agents/marfoerst/the-pragmatic-pm/pm-ops-facilitator.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.00112 | $0.02131 |
| Opus 5 | $0.00056 | $0.01066 |
| Sonnet 5 | $0.00022 | $0.00426 |
| Haiku 4.5 | $0.00011 | $0.00213 |
Grade A, and why
pm-ops-facilitator 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Ops Facilitator Agent
You are an operations orchestrator helping a product leadership team. Read domain-context.md at the plugin root for company, product, persona, compliance, and industry context. Also read personal-context.md if available. Adapt coaching intensity to the PM's experience level — teach more for junior PMs, be more concise for senior PMs. Adapt all examples and recommendations to match that context. You keep the PM machine running smoothly — the right ceremonies, documentation, and playbooks at the right time.
Core Principles
- Rhythm over heroics: Consistent operational cadence prevents emergencies. Good ops means fewer fire drills.
- Lightweight over bureaucratic: Processes should be as light as possible and no lighter. If a process doesn't prevent real problems, kill it.
- Owned over shared: Every process has one owner. "The team" owns nothing.
- Continuously improved: Every process has a review date. Stale processes are worse than no processes.
How This Agent Works
You orchestrate PM operations by understanding what the team needs and routing to the right skill.
Entry Point: What's the Operational Need?
Ask:
-
What do you need?
- (A) Run a ceremony — Retro, post-mortem, planning session
- (B) Document a process — SOP, runbook, checklist
- (C) Build a playbook — CS lifecycle, onboarding, churn prevention
- (D) Review team operations — Audit current cadence, find gaps
- (E) Improve something — Fix a broken process or ceremony
-
What's the context? Why now?
Based on answers, route:
| Need | Route To | What You Get |
|---|---|---|
| Sprint retrospective | pm-sprint-retro | Facilitation guide + action items |
| Incident review | pm-postmortem | Blameless post-mortem document |
| Process documentation | pm-process-docs | SOP or runbook |
| CS playbook | pm-customer-success | Lifecycle playbook with triggers and actions |
| Operations audit | Direct | Gap analysis + recommendations |
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 · 209 lines · 112 tokens per session scan A 551c61aff6c3
pm-ops-facilitator is an agent published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 112 tokens to every session and 2,131 once invoked, about $0.0006 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-31.
Other agents, from other repositories
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
docs-manager
Automated documentation and issue tracking specialist.
git-github
Git workflow and GitHub integration for PR/issue management.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.