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 mattgierhart/PRD-driven-context-engineering --skill prd-v03-pricing-modelgit clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineeringWrote 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/mattgierhart/prd-driven-context-engineering/prd-v03-pricing-model)<a href="https://agentmods.dev/skills/mattgierhart/prd-driven-context-engineering/prd-v03-pricing-model"><img src="https://agentmods.dev/badge/skills/mattgierhart/prd-driven-context-engineering/prd-v03-pricing-model/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/mattgierhart/prd-driven-context-engineering/prd-v03-pricing-model"><img src="https://agentmods.dev/badge/skills/mattgierhart/prd-driven-context-engineering/prd-v03-pricing-model.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.02876 |
| Opus 5 | $0.00056 | $0.01438 |
| Sonnet 5 | $0.00022 | $0.00575 |
| Haiku 4.5 | $0.00011 | $0.00288 |
Grade A, and why
prd-v03-pricing-model 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 9d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Model Selection
Position in HORIZON workflow: v0.2 Product Type Classification → v0.3 Pricing Model Selection → v0.3 Moat Articulation
Consumes
This skill requires prior work from v0.2-v0.3:
- BR-* product type entry (from Product Type Classification) — Determines which pricing model makes sense
- CFD-* competitive intelligence entries (from Competitive Landscape Mapping) — Competitor pricing, WTP signals
- BR-* moat entries (from Moat Definition, parallel v0.3 work) — Price as potential moat element
- KPI-* outcome entries (from Outcome Definition, parallel v0.3 work) — Success metrics tied to pricing
- Cost structure estimates (from own analysis) — Unit economics to validate price floors
This skill assumes v0.2 competitive analysis is complete and product type is defined.
Produces
This skill creates/updates:
- BR-PRC-* entries (pricing constraints) — Rules governing price floors, ceilings, discounts
- BR-PKG-* entries (packaging rules) — Tier boundaries and feature gates
- BR-CMP-* entries (competitive positioning) — Price anchor targets and undercut thresholds
- Pricing model artifact — Named decision: "We will use [Model] because [evidence]" with tier definitions
All BR pricing entries should include:
confidence: 2-3/5(based on WTP evidence tier and competitor benchmarks, not assumptions)- Evidence source (competitor pricing, customer interviews, cost structure)
- Forward target: "Would move to 4/5 if real customers validate WTP"
Example pricing rule entry:
BR-PRC-001: Entry Price Floor
Rule: Entry tier never below $15/mo (annual) or $19/mo (monthly)
Confidence: 2/5 (source: CAC-estimate + competitor-benchmarks)
Rationale: Below $15/mo, CAC payback exceeds 6 months, unsustainable
Enforcement: Stripe product configuration, pricing page, contract templates
Evidence:
- CFD-042 (competitor pricing): Similar tools start at $15-25/mo
- KPI-001 (outcome): CAC estimate $45, need 3-month payback = $15/mo minimum
Enforcement: Set in Stripe, document in pricing page, enforce in sales contracts
Exception: Founding customer 50% discount (must be approved by founder)
Next Target: "Would move to 4/5 if 5+ paying customers validate willingness at $15/mo"
---
BR-CMP-002: Competitive Undercut Threshold
Rule: Maintain ≥50% savings vs [Competitor Name] at SMB level (5 users)
Confidence: 3/5 (source: competitor-pricing + 2-SMB-interviews)
Rationale: Price advantage is core differentiator for SMB segment (per product type: UNDERCUT)
Enforcement: Quarterly competitive price audit; triggers price review if competitor drops
Evidence:
- BR-001 (product type: Undercut)
- CFD-015 (value hypothesis): SMB would save $12,500/year at target price
- CFD-042 (competitor pricing): Competitor at $30/user/mo = $1,800/year for SMB
Exception: If competitor drops price, floor (BR-PRC-001) takes precedence
Next Target: "Would move to 4/5 if SMB cohort pays premium for our service over incumbent"
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 273 lines · 112 tokens per session scan A b7f71d110b14
prd-v03-pricing-model is a skill published in the GitHub repository mattgierhart/PRD-driven-context-engineering (182 stars, last pushed 9d ago), licensed MIT. It adds 112 tokens to every session and 2,876 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-30.
Other skills, from other repositories
vertical-retail
Retail & e-commerce domain knowledge for SMB storefront products (storefront, inventory, pricing, cart-recovery). Codifies the vocabulary (SKU vs variant, reorder point, COGS/margin, ATS, AOV), the non-obvious rules (Shopify owns the storefront — don't fight it head-on; the wedge is multichannel inventory + reorder…
vertical-restaurants
Domain-knowledge primer for the restaurants & hospitality vertical (dine-in, pickup, delivery). Gives architect and pm the vocabulary, non-obvious operating rules, must-model entities, and incumbent landscape so a restaurant-product spec isn't naive about modifiers, 86'd items, aggregator commissions, tip law, and…
api-commerce-stripe
Stripe payment processing — Checkout Sessions, Payment Intents, subscriptions, webhooks, Connect, customer management, error handling.
form-cro
When the user wants to optimize any form that is NOT signup/registration — lead capture, contact, demo request, application, survey, or checkout forms; "form friction," "form completion rate," "form abandonment," "too many fields," "nobody fills out our form." For signup/registration forms, see signup-flow-cro. For…
marketplace-design
Use when someone asks how a catalogue, listing grid, comparison view, detail page, or transaction bridge should help participants discover and choose in a marketplace. Produces information-architecture specifications for search, filters, listings, comparison, and the path to transaction. Use conversion-design for a…
paywall-upgrade-cro
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates — "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached," "free users won't upgrade." Covers in-product upgrade moments where the user has already experienced value — distinct…