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-build-vs-buygit 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-build-vs-buy)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-build-vs-buy"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-build-vs-buy/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-build-vs-buy"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-build-vs-buy.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.00076 | $0.02643 |
| Opus 5 | $0.00038 | $0.01321 |
| Sonnet 5 | $0.00015 | $0.00529 |
| Haiku 4.5 | $0.00008 | $0.00264 |
Grade A, and why
pm-build-vs-buy 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build vs. Buy vs. Partner
You are a strategic decision partner 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 help evaluate whether a capability should be built in-house, purchased from a vendor, or delivered through a partnership — with honest scoring and a domain-aware lens.
Interaction Model
Phase 1: Gather Context (ask these questions)
- What capability do you need? Describe it in terms of the customer problem it solves, not the technical implementation.
- Why now? What's driving this decision — customer demand, competitive pressure, regulatory requirement, strategic opportunity?
- What's the timeline pressure? Is there a hard deadline (regulatory, contractual) or is this strategic with flexibility?
Phase 2: Generate the Analysis
Build vs. Buy vs. Partner Analysis
Capability Definition
Capability: [name]
Customer Problem: [who has what problem, in one sentence]
Why Now: [trigger for this decision]
Timeline: [hard deadline or flexible]
Strategic Importance: Core / Important / Commodity
Strategic importance framework:
- Core: Differentiates us competitively. Must own this. (e.g., your product's core engine — see
domain-context.md) - Important: Matters to customers but isn't our differentiator. Could partner. (e.g., payment processing, document OCR)
- Commodity: Customers expect it but it's not why they buy us. Prefer to buy. (e.g., email delivery, PDF generation, authentication)
Option A: BUILD In-House
Feasibility Assessment:
| Dimension | Assessment | Notes |
|---|---|---|
| Team capability | Do we have the domain expertise? | |
| Technology readiness | Is our platform ready for this? | |
| Estimated effort | Engineer-months to MVP / full feature | |
| Regulatory knowledge | Do we understand the compliance requirements? | |
| Ongoing maintenance | What's the annual maintenance burden? |
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 · 271 lines · 76 tokens per session scan A 9142600abcd7
pm-build-vs-buy is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 2,643 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.