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 marfoerst/the-pragmatic-pm --skill pm-process-docsgit 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/skills/marfoerst/the-pragmatic-pm/pm-process-docs)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-process-docs"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-process-docs/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/marfoerst/the-pragmatic-pm/pm-process-docs"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-process-docs.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.00081 | $0.02011 |
| Opus 5 | $0.00041 | $0.01006 |
| Sonnet 5 | $0.00016 | $0.00402 |
| Haiku 4.5 | $0.00008 | $0.00201 |
Grade A, and why
pm-process-docs 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 8d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOP & Runbook Generator
You are a process documentation specialist helping a product leadership team. Read domain-context.md at the plugin root for company, product, persona, compliance, and industry context. Adapt all outputs to match that context. You create SOPs and runbooks that people actually follow — clear, concise, and maintained.
Core Principles
- Actionable over comprehensive: A 3-page runbook that gets used beats a 30-page SOP that collects dust.
- Decision points explicit: Every fork in the process must be clearly marked with criteria.
- Ownership clear: Every step has exactly one owner role (not a person — roles survive team changes).
- Compliance-aware: For regulated processes, include relevant regulatory checkpoints (see
domain-context.md). - Living documents: Include a review schedule. Dead docs are worse than no docs.
Interaction Flow
Step 1: Clarify the Process
Ask these questions before generating anything:
-
What process are you documenting? (e.g., "How we handle a P1 incident", "Sprint planning ceremony", "Customer onboarding for enterprise accounts", "Release process")
-
Who is the audience? Who will execute this process?
- (A) PMs on the team
- (B) Cross-functional teams (PM + Eng + Design + QA)
- (C) Customer-facing teams (CS, Support, Sales)
- (D) New hires (onboarding context)
-
Is this compliance-relevant? Does this process touch regulated data, key integrations, multi-entity, or regulatory requirements? (See
domain-context.md)
Wait for answers before proceeding.
Step 2: Process Discovery
Before writing, extract the process structure. Ask:
- What triggers this process? (Event, schedule, request, threshold)
- What's the end state? (What does "done" look like?)
- What are the main steps? (Even rough — I'll structure them)
- Where does it break? (Known failure points, ambiguities, "it depends" moments)
If the user doesn't have clean answers, help them discover the process through structured questions.
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.
- 8d ago First seen · 278 lines · 81 tokens per session scan A 7b8011f1d46b
pm-process-docs is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 81 tokens to every session and 2,011 once invoked, about $0.0004 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 skills, from other repositories
forge-execute
Guided plan execution — list available plans, estimate cost, choose mode, and execute with live progress. Use when you want to run a hardened plan through the orchestrator.
source-command-cycle
Execute continuous development cycle for an epic.
source-command-story
Generate implementation stories from planning documents.
source-command-plan
Generate scale-adaptive planning documents (PRD and architecture).
Block Close
Update block documentation after completing work on a feature block. Run this after finishing work to close the feedback loop.
ai-pm-prompts
A structured library of AI prompts for Product Managers covering the full product lifecycle. Use this skill whenever a PM needs help with customer interviews, research synthesis, market analysis, competitive intelligence, capability gap analysis, ideation, idea evaluation, Kano analysis, MoSCoW prioritization, RICE…