pricing

A pricing and monetisation strategy workflow for deciding what to charge, how to group plans, and how customers pay for a product or service.

In plain words
What is it for?
Use it to design pricing tiers, freemium plans, free trials, value metrics, price increases, and other monetisation decisions.
Why use it?
It helps connect prices and plan structure to customer value, alternatives, willingness to pay, and business goals.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/patrickserrano/lacquer/pricing
Any agent
npx skills add patrickserrano/lacquer --skill pricing
Clone the repo
git clone --depth 1 https://github.com/patrickserrano/lacquer

Made for: Claude Code, Codex.

Per session 206 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,055 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00206 $0.03055
Opus 5 $0.00103 $0.01528
Sonnet 5 $0.00041 $0.00611
Haiku 4.5 $0.00021 $0.00305

Measured 2d ago against content hash 6cb88c2e9443, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pricing 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 2d 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.

Origin

This is a copy

100% identical to pricing — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

core/skills/pricing/SKILL.md · 296 lines

How it starts

The opening of the file, as written. The whole thing — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pricing Strategy

You are an expert in SaaS pricing and monetization strategy. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Business Context

  • What type of product? (SaaS, marketplace, e-commerce, service)
  • What's your current pricing (if any)?
  • What's your target market? (SMB, mid-market, enterprise)
  • What's your go-to-market motion? (self-serve, sales-led, hybrid)

2. Value & Competition

  • What's the primary value you deliver?
  • What alternatives do customers consider?
  • How do competitors price?

3. Current Performance

  • What's your current conversion rate?
  • What's your ARPU and churn rate?
  • Any feedback on pricing from customers/prospects?

4. Goals

  • Optimizing for growth, revenue, or profitability?
  • Moving upmarket or expanding downmarket?

Pricing Fundamentals

The Three Pricing Axes

1. Packaging — What's included at each tier?

  • Features, limits, support level
  • How tiers differ from each other

2. Pricing Metric — What do you charge for?

  • Per user, per usage, flat fee
  • How price scales with value

3. Price Point — How much do you charge?

  • The actual dollar amounts
  • Perceived value vs. cost

Value-Based Pricing

Price should be based on value delivered, not cost to serve:

  • Customer's perceived value — The ceiling
  • Your price — Between alternatives and perceived value
  • Next best alternative — The floor for differentiation
  • Your cost to serve — Only a baseline, not the basis

Key insight: Price between the next best alternative and perceived value.

Read the full file on GitHub · 296 lines

Files

What ships with it

5 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.

Changes

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.

  1. 2d ago First seen · 296 lines · 206 tokens per session scan A 6cb88c2e9443

Subscribe to this mod's changes

pricing is a skill published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed 2d ago), licensed MIT. It adds 206 tokens to every session and 3,055 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pricing, differing in 0 lines, and is treated as a copy.