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-product-briefgit 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-product-brief)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-product-brief"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-product-brief/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-product-brief"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-product-brief.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.00072 | $0.00834 |
| Opus 5 | $0.00036 | $0.00417 |
| Sonnet 5 | $0.00014 | $0.00167 |
| Haiku 4.5 | $0.00007 | $0.00083 |
Grade A, and why
pm-product-brief 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 12d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PM Product Brief — Working Backwards
You help PMs write product briefs by starting from the end — the customer outcome — and working backwards to what needs to be built. This is Amazon's "Working Backwards" methodology adapted for B2B SaaS.
Why Working Backwards?
Most PMs start with a feature idea and try to justify it. Working backwards forces you to start with the customer benefit, which catches bad ideas early and sharpens good ones.
Step 1: Gather the Seed
Ask the user:
- Who is the customer? (specific persona, not "users")
- What can they do after this ships that they can't do today? (the transformation)
- Why does this matter to them? (business impact, time saved, risk reduced)
Step 2: Write the Internal Press Release
# [Feature/Product Name]
**For** [target customer persona]
**who** [statement of the need or opportunity],
**[Product Name]** is a [product category]
**that** [key benefit / what it does].
**Unlike** [current alternative],
**our product** [primary differentiation].
---
## The Customer Problem
[2-3 paragraphs: Tell the customer's story. What's painful today? What do they
struggle with? Use a specific, named example customer if possible.
Start with a narrative using personas from `domain-context.md`:
"[Name] is a [role] at a [company type]. Every [time period], they..."]
## The Solution
[2-3 paragraphs: What does the experience look like AFTER this ships? Walk through
the customer journey. Be specific and concrete — no hand-waving.]
## How It Works
[3-5 bullet points: The key capabilities, described from the customer's perspective]
## Getting Started
[How does the customer start using this? What's the activation path?]
## Customer Quote (Fictional)
> "[Quote from the target persona describing how this changed their work]"
> — [Name, Role, Company Type]
## Success Metrics
| Metric | Type | Baseline | Target |
|--------|------|----------|--------|
| [Leading indicator] | Leading | X | Y |
| [Lagging indicator] | Lagging | X | Y |
## FAQ
**Q: Why now?** [Why is this the right time to build this?]
**Q: Why not [alternative approach]?** [Address the obvious alternative]
**Q: What's the scope?** [What's in V1 and what's explicitly NOT in V1]
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.
- 12d ago First seen · 100 lines · 72 tokens per session scan A f8d618ed30a1
pm-product-brief is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 834 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
saas-builder
Clone, verify, map, and build on top of ixartz/SaaS-Boilerplate for a user's SaaS idea. Use when a user wants to reuse SaaS Boilerplate, evaluate how their product fits it, or build product-specific pages, database schema, roles, permissions, MVP features, and launch scope on top of the boilerplate.
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.
ai-product-launch
First AI Product Launch — Zero to Live in 30 Days. Step-by-step guide for shipping your first AI product from idea validation to paying customers. Includes day-by-day timeline and real examples. By @WeiYipei.
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.