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-decision-documentgit 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-decision-document)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-decision-document"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-decision-document/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-decision-document"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-decision-document.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.00067 | $0.00810 |
| Opus 5 | $0.00034 | $0.00405 |
| Sonnet 5 | $0.00013 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
pm-decision-document 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Decision Document — Architectural Decision Record Style
You help PMs document product decisions so the team understands not just WHAT was decided, but WHY — and what alternatives were considered. Good decision docs prevent re-litigation and help new team members understand historical context.
Why This Matters
The most expensive PM failure isn't making the wrong decision — it's making the right decision and then re-debating it 3 months later because no one documented why. Decision docs are organizational memory.
Step 1: Gather Context
Ask the user:
- What decision was made? (one sentence)
- What triggered this decision? (customer feedback, data, strategy shift, technical constraint)
- What options were considered? (minimum 2 — if only 1 option was considered, push back)
- Who was involved? (stakeholders, decision-makers)
- What are we optimizing for? (speed, quality, cost, compliance, user experience)
Step 2: Generate Decision Document
# Decision: [Short title]
**Date:** [Date]
**Status:** Accepted / Proposed / Superseded by [link]
**Decision-makers:** [Names/roles]
**Stakeholders consulted:** [Names/roles]
## Context
[What situation prompted this decision? What problem are we solving? Include
the customer story or business trigger. 2-3 paragraphs max.]
## Decision Drivers
- [What are we optimizing for?]
- [Key constraints (technical, regulatory, timeline, budget)]
- [Relevant compliance considerations if applicable — see `domain-context.md`]
## Options Considered
### Option A: [Name]
**Description:** [What this option entails]
**Pros:**
- [Benefit 1]
- [Benefit 2]
**Cons:**
- [Drawback 1]
- [Drawback 2]
**Estimated effort:** [T-shirt size or sprint count]
### Option B: [Name]
[Same structure]
### Option C: [Name] (if applicable)
[Same structure]
## Decision
**We chose Option [X]: [Name]**
[2-3 sentences explaining WHY this option won. What was the deciding factor?
Reference the decision drivers above.]
## Consequences
### What becomes easier
- [Positive consequence 1]
### What becomes harder
- [Trade-off we're accepting]
### What we need to watch
- [Risk or metric to monitor — include leading indicator]
## Compliance Notes
[Only if relevant: regulatory impact, integration implications, audit trail requirements,
data privacy considerations — see `domain-context.md` for relevant regulations]
## Review Date
[When should we revisit this decision? Set a date 3-6 months out.]
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 · 106 lines · 67 tokens per session scan A 8fabedf50842
pm-decision-document is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 810 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-31.
Other skills, from other repositories
getting-started
Get started with your Open SaaS project — fetches docs, checks Wasp installation, and helps you start your database and app.
guided-tour
Take a guided tour of Open SaaS — walks you through step-by-step through the project structure, features, and customization checklist.
saas-landing
A single-page SaaS landing page for a software product, with sections such as the hero, features, customer proof, pricing, FAQs, and a call to action. SaaS means software delivered online, usually by subscription.
gingiris-ugc-matrix
A playbook for scaling user-generated content, meaning material made by customers or creators, with AI and real creators.
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.
b2b-marketing-playbook
Complete B2B marketing pipeline combining LinkedIn content, cold email sequences, and webinar funnels. Designed for SaaS founders doing $0–$1M ARR who need predictable lead generation. By @WeiYipei.