pricing-strategy

pricing-strategy is a skill for Claude Code, Codex from L-LesterYu/OpenClaw-hot-skills-zh. It costs 86 tokens per session (4,695 once invoked), scanned A, a copy of pricing-strategy, MIT.

A guide to deciding how a product is priced, packaged, and sold. It covers choices such as pricing tiers, free trials, freemium plans, and the amount customers may be willing to pay.

In plain words
What is it for?
Use it to design or change pricing tiers, study willingness to pay, plan price increases, and choose a pricing model for software or other products.
Why use it?
It helps teams make pricing decisions based on customer value, competitors, business goals, and buying behaviour. This reduces the risk of setting prices or plans without enough evidence.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Good fit Use it to design or change pricing tiers, study willingness to pay, plan price increases, and choose a pricing model for software or other products.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/l-lesteryu/openclaw-hot-skills-zh/pricing-strategy
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.

Any agent
npx skills add L-LesterYu/OpenClaw-hot-skills-zh --skill pricing-strategy
Clone the repo
git clone --depth 1 https://github.com/L-LesterYu/OpenClaw-hot-skills-zh

Made for: Claude Code, Codex.

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

agentmods badge for pricing-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/l-lesteryu/openclaw-hot-skills-zh/pricing-strategy/github.svg)](https://agentmods.dev/skills/l-lesteryu/openclaw-hot-skills-zh/pricing-strategy)
Your own site
<a href="https://agentmods.dev/skills/l-lesteryu/openclaw-hot-skills-zh/pricing-strategy"><img src="https://agentmods.dev/badge/skills/l-lesteryu/openclaw-hot-skills-zh/pricing-strategy/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.

agentmods 80×15 button for pricing-strategy

Your own site · 80×15
<a href="https://agentmods.dev/skills/l-lesteryu/openclaw-hot-skills-zh/pricing-strategy"><img src="https://agentmods.dev/badge/skills/l-lesteryu/openclaw-hot-skills-zh/pricing-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,695 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00086 $0.04695
Opus 5 $0.00043 $0.02348
Sonnet 5 $0.00017 $0.00939
Haiku 4.5 $0.00009 $0.00470

Measured 9d ago against content hash 44cd0b6d3dfc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

pricing-strategy 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.

Origin

This is a copy

100% identical to pricing-strategy — 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.

skills/marketing-skills-zh/references/pricing-strategy/SKILL.md · 711 lines

How it starts

The opening of the file, as written. The whole thing — 711 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 with access to pricing research data and analysis tools. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.

Before Starting

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?
  • What makes you different/better?

3. Current Performance

  • What's your current conversion rate?
  • What's your average revenue per user (ARPU)?
  • What's your churn rate?
  • Any feedback on pricing from customers/prospects?

4. Goals

  • Are you optimizing for growth, revenue, or profitability?
  • Are you trying to move upmarket or expand downmarket?
  • Any pricing changes you're considering?

Pricing Fundamentals

The Three Pricing Axes

Every pricing decision involves three dimensions:

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
  • The perceived value vs. cost

Value-Based Pricing Framework

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

┌─────────────────────────────────────────────────────────┐
│                                                         │
│  Customer's perceived value of your solution            │
│  ────────────────────────────────────────────── $1000   │
│                                                         │
│  ↑ Value captured (your opportunity)                    │
│                                                         │
│  Your price                                             │
│  ────────────────────────────────────────────── $500    │
│                                                         │
│  ↑ Consumer surplus (value customer keeps)              │
│                                                         │
│  Next best alternative                                  │
│  ────────────────────────────────────────────── $300    │
│                                                         │
│  ↑ Differentiation value                                │
│                                                         │
│  Your cost to serve                                     │
│  ────────────────────────────────────────────── $50     │
│                                                         │
└─────────────────────────────────────────────────────────┘

Read the full file on GitHub · 711 lines

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. 9d ago First seen · 711 lines · 86 tokens per session scan A 44cd0b6d3dfc

Subscribe to this mod's changes

pricing-strategy is a skill published in the GitHub repository L-LesterYu/OpenClaw-hot-skills-zh (54 stars, last pushed 5mo ago), licensed MIT. It adds 86 tokens to every session and 4,695 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pricing-strategy, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens