Agent skill

Pricing

by ericrisco in ericrisco/rsc-harness

A skill your agent uses when setting or resetting what a product or service charges and how it is packaged — list price, margin floor, tiers, the value metric, the pricing model (flat, seat, usage…

MITAuto-check passedSales & Support

Install Pricing

skills CLI
$ npx skills add ericrisco/rsc-harness --skill pricing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ericrisco/rsc-harness pricing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pricing .claude/skills/pricing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pricing
GitHub stars
174
Token cost
~2.6k tokens
SKILL.md length
1,315 words
Files
6 (incl. scripts, references)
Skills in repo
233
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when setting or resetting what a product or service charges and how it is packaged — list price, margin floor, tiers, the value metric, the pricing model (flat, seat, usage…

  • Works in 7 steps: Floor (cost). Compute fully-loaded unit… → Ceiling (willingness-to-pay). What the… → Value metric. The thing the customer… → …
  • Resetting what a product
  • SKILL.md covers The spine — run it in this order, Margin math you must not get…, Pick the model and Package the tiers, plus 6 more sections
  • Runs Shell scripts from its folder

What it does

Pricing is an agent skill from ericrisco/rsc-harness. Use when setting or resetting what a product or service charges and how it is packaged — list price, margin floor, tiers, the value metric, the pricing model (flat, seat, usage, outcome or hybrid), discount rules and purchasing-power localisation. NOT issuing the actual bill (that is invoicing), NOT implementing prices in a billing system (that is stripe).

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `evals/README.md`, `evals/cases.yaml` and `references/localization.md`).

It sits in Sales & Support, covering Pricing strategy and Internationalization. It works with Stripe. The repository describes itself as: Your agent invents things because it has no memory, and can't touch your database because it has no arms. rsc is the meta-harness that gives it both, plus the trade to know the… The licence is MIT.

When your agent uses it

  • Resetting what a product
  • Service charges and how it is packaged — list price
  • The value metric
  • The pricing model (flat

Example prompts

  • “/pricing”

Requirements

  • A Bash shell

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Floor (cost). Compute fully-loaded unit cost (COGS + must-cover). Below this you lose money on every sale — why first: it is the one…
  2. Ceiling (willingness-to-pay). What the buyer will pay before walking — why next: it bounds everything above the floor; price between floor…
  3. Value metric. The thing the customer buys more of as they grow (seats, usage, outcomes) — why before tiers: it is the spine the tiers hang…
  4. Model. Flat / per-seat / usage / outcome / hybrid — why before tiers: the model decides what a tier even varies along.
  5. Tiers. Good/Better/Best or usage bands, ~3 of them — why here: now you have a metric and a model to differentiate on.
  6. Discount floor. Max discount = how far list can fall before hitting the cost floor — why after price: a discount rule needs a list price…
  7. Localize (optional). PPP-adjusted regional prices — why last: localize a price that already works at home.

What it can do on your machine

Read from SKILL.md and the folder at commit e3d5b33. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pricing loads about 2.6k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 93 tokens; SKILL.md has 1,315 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~93
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from ericrisco/rsc-harness at commit e3d5b33, republished under its MIT licence (© ericrisco). 1,315 words, ~2,605 tokens.

Download SKILL.mdSave it as .claude/skills/pricing/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
pricing
description
Use when setting or resetting what a product or service charges and how it is packaged — list price, margin floor, tiers, the value metric, the pricing model (flat, seat, usage, outcome or hybrid), discount rules and purchasing-power localisation. NOT issuing the actual bill (that is `invoicing`), NOT implementing prices in a billing system (that is `stripe`).
tags
pricing, packaging, margin, tiers, discounting, value-metric, willingness-to-pay, ppp
recommends
invoicing, stripe, unit-economics, proposals, forecasting, sales-pipeline
origin
risco

Pricing

You decide two things here: the number (the list price) and the shape (packaging, tiers, model, and the floor underneath each price). You produce a price card — a table where every tier has a price, a cost, a value metric, and a margin that someone else can recompute and disagree with. That artifact is the deliverable; opinions without a recomputable margin are not.

You do not charge the money (that is ../invoicing/SKILL.md), build the billing objects (that is ../stripe/SKILL.md), record revenue in the books, or validate the number against acquisition cost (that is ../unit-economics/SKILL.md). Stay on the decision: what should this cost, and how is it boxed.

The spine — run it in this order

The order matters because each step constrains the next. Skip a step and you set a price you cannot defend.

  1. Floor (cost). Compute fully-loaded unit cost (COGS + must-cover). Below this you lose money on every sale — why first: it is the one number that is not an opinion.
  2. Ceiling (willingness-to-pay). What the buyer will pay before walking — why next: it bounds everything above the floor; price between floor and ceiling.
  3. Value metric. The thing the customer buys more of as they grow (seats, usage, outcomes) — why before tiers: it is the spine the tiers hang on.
  4. Model. Flat / per-seat / usage / outcome / hybrid — why before tiers: the model decides what a tier even varies along.
  5. Tiers. Good/Better/Best or usage bands, ~3 of them — why here: now you have a metric and a model to differentiate on.
  6. Discount floor. Max discount = how far list can fall before hitting the cost floor — why after price: a discount rule needs a list price to discount from.
  7. Localize (optional). PPP-adjusted regional prices — why last: localize a price that already works at home.

If you cannot answer step 1, stop and get the cost. Everything downstream is guesswork without it.

Margin math you must not get wrong

Markup and margin use different denominators. Conflating them is the single most common pricing error.

text
markup %  = (price - cost) / cost      <- denominator is COST
margin %  = (price - cost) / price     <- denominator is PRICE

Reference points to sanity-check any card (verify.sh uses these):

MarkupMargin
30%23%
43%30%
100%50%

A 50% markup is only a 33% margin. A 50% margin needs a 100% markup. They diverge fast.

text
Bad:  cost $70, want "30% margin", apply 30% markup -> price $91
      actual margin = (91-70)/91 = 23%. You undershot by 7 points.
Good: cost $70, want 30% margin -> price = cost / (1 - 0.30)
      = 70 / 0.70 = $100. Margin = (100-70)/100 = 30%. Correct.

The price-from-margin formula: price = cost / (1 - target_margin). Memorize it; never apply a markup percentage when someone said "margin".

Pick the model

Decide the model before drawing tiers — it determines what the tiers vary along.

ModelUse whenValue metricWatch out
FlatOne persona, predictable use, simple sellnone (one price)Leaves money on the table at the high end
Per-seatValue scales with users; collaboration toolsseatsEroding — buyers cap seats and share logins; revenue stalls
Usage / consumptionValue scales with volume; infra, API, AIunits consumedEstimate anxiety + overage shock; needs a meter
Outcome-basedYou can attribute a result (resolutions, leads)outcomes deliveredAttribution disputes; needs a credible counter
HybridPlatform value + variable use (most AI products)base + usage/outcomeTwo dials to explain; keep the base legible

The market is moving off pure per-seat. ~85% of SaaS used some usage-based pricing by 2024 (up from ~30% in 2019), and Gartner expects ~40% of enterprise SaaS spend on usage/agent/outcome models by 2030. If you are defaulting to per-seat for an AI product, justify it.

AI-COGS caveat — the margin assumption changes. Classic SaaS runs 80-90% gross margin. AI products run 50-60% because every query has real compute cost. A "we'll just take 80% margin" plan is wrong for AI: the cost floor (step 1) becomes load-bearing, and you reprice when compute cost moves. See references/pricing-models.md for the outcome credit + overage formula (platform fee ≈ 2× delivery cost, e.g. $12K/yr incl. 100 resolutions then $5K per additional 100) and seat-compression math.

Package the tiers

Good/Better/Best is the dominant SaaS shape; the average SaaS company offers ~3.5 tiers. Three is the safe default — enough to anchor, not enough to paralyze.

  • Distinct on all three: each tier must differ in features, limits, and price. If two tiers share limits, you have one tier with a typo.
  • Value metric is the axis. Tiers move along the value metric you picked in step 3 (more seats, more usage, more outcomes), not a random feature grab-bag.
  • Anchor with the top tier. The Best tier makes Better look reasonable; it is doing a job even if few buy it.
  • Name the limit, not just the feature. "10 projects" beats "projects" — a limit is what a buyer hits and upgrades on.
text
Good     Better        Best
$0/$X    $Y            $Z (anchor)
3 seats  25 seats      unlimited seats
1K calls 50K calls     500K calls + overage
email    + Slack       + SSO, SLA, CSM

Set the discount floor

A discount needs a floor, not a vibe. Reps will give away the business if the only rule is "use judgment".

  • Floor = COGS + must-cover cost for that tier. Below it the deal loses money.
  • Max discount % = (list − floor) / list. This is the largest discount a rep can give without burning margin.
  • No sign-off, no floor-break. Discounting below the floor requires explicit approval, recorded. The floor is the deal-desk's hard stop.
text
Tier "Better": list $1,000, cost floor $400
max discount = (1000 - 400) / 1000 = 60%
A rep offering 35% off ($650) is fine; 65% off ($350) breaks the floor -> sign-off.
Show full SKILL.md (496 more words)Show less

Localize (optional branch)

Only if you sell across markets. Localizing beats raw FX conversion — PPP-adjusted regional pricing lifts revenue ~30% over straight currency math.

  • Start from home list price × PPP factor (World Bank / OECD), not the spot exchange rate.
  • Charm vs round by market: $99-style charm prices convert in US/DE/AU; round numbers are preferred in JP/CN/BR.
  • Review quarterly to semiannually — PPP and FX drift.
  • Guard against VPN geo-arbitrage with local payment-method / billing-address checks.

The per-region rounding conventions, PPP sourcing, and arbitrage guards live in references/localization.md — most operators skip this branch, so it is offloaded.

Willingness-to-pay, fast

You usually do not need a survey. Two paths:

  • Cheap default: raise the price until you feel friction (longer sales cycles, more "too expensive"). If nobody pushes back, you are underpriced.
  • When the number is high-stakes: run a Van Westendorp four-question survey — at what price is this (1) too expensive to consider, (2) getting expensive but worth a look, (3) good value, (4) so cheap you doubt the quality. The curve intersections give an acceptable price band and an optimal point. Use it before committing a number you cannot easily change.

Anti-patterns

Anti-patternWhy it is wrongDo instead
Applying markup % when someone said "margin"30% markup is only a 23% margin — you undershoot every timeprice = cost / (1 - margin); recompute, never assume
Cost-plus only, ignoring willingness-to-payLeaves money on the table or prices below what buyers gladly payFloor from cost, ceiling from WTP, set price between
Five+ tiers to "cover everyone"Choice paralysis; nobody self-selects~3 tiers, distinct on features + limits + price
Per-seat by default for an AI productSeat revenue erodes and AI COGS breaks the 80% assumptionPick the value metric first; consider usage/outcome/hybrid
Discount "by judgment" with no floorReps give away the business deal by dealFloor = COGS+must-cover; max discount = (list−floor)/list; below = sign-off
Converting price by spot FX across marketsMispriced vs local purchasing power; ~30% revenue left behindPPP factor × home price; round per local convention
Assuming 80-90% margin for AI computeReal per-query COGS makes it 50-60%; you over-promise marginUse the cost floor as load-bearing; reprice when compute moves

The price card (the artifact)

Emit a price-card.csv (or .md table / .yaml) — one row per tier:

csv
tier,price,cost,value_metric,margin
Good,29,11,seats,0.62
Better,99,38,seats,0.62
Best,299,110,seats,0.63

Rules the card must satisfy:

  • Every row has price, cost, value_metric, and a stated margin.
  • Stated margin matches recomputed (price − cost) / price within 0.5pt.
  • No price <= cost and no price < floor.
  • margin is a margin, not a markup (the classic conflation).

scripts/verify.sh <price-card> recomputes every margin, flags any tier below its floor, and warns when a stated "margin" is actually a markup. Run it before you ship the card. It is read-only and exits 0 on an empty or clean card.

Siblings

  • Charge it / format the bill -> ../invoicing/SKILL.md
  • Build products & prices in the billing system -> ../stripe/SKILL.md
  • Validate the number against CAC / payback -> ../unit-economics/SKILL.md
  • Put the price in front of one named buyer -> ../proposals/SKILL.md
  • Project revenue from the price -> ../forecasting/SKILL.md
  • Run the deal and pipeline stages -> ../sales-pipeline/SKILL.md

© ericrisco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in skills/pricing of ericrisco/rsc-harness.

  • SKILL.md
  • evals/README.md
  • evals/cases.yaml
  • references/localization.md
  • references/pricing-models.md
  • scripts/verify.sh

Open the folder on GitHubat commit e3d5b33

Compare with similar skills

Pricing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pricing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pricing this skillericrisco/rsc-harness174—~2.6kAutomated safety check: PassMIT
Monetizationsickn33/agentic-awesome-skills47k2 repos~3kAutomated safety check: PassMIT
Pricing StrategyOpenClaudia/openclaudia-skills713—~1.8kAutomated safety check: PassMIT
Suede PricingJasonColapietro/suede-creator-skills127—~2.4kAutomated safety check: PassMIT
Competitor Price TrackerOneWave-AI/claude-skills3282 repos~372Automated safety check: PassMIT
Deal Pricingjeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: NotesMIT

Similar skills

  • Monetization

    sickn33/agentic-awesome-skills

    Estrategia e implementacao de monetizacao para produtos digitais - Stripe, subscriptions, pricing experiments, freemium, upgrade flows, churn prevention, revenue optimization e modelos de negocio…

    47k GitHub starsUsed in 2 repos~3k tokens
    Sales & SupportAuto-check passed
  • Pricing Strategy

    OpenClaudia/openclaudia-skills

    Optimize pricing pages, pricing models, and pricing strategy.

    713 GitHub stars~1.8k tokensUpdated 21 days ago
    Sales & SupportAuto-check passed
  • Suede Pricing

    JasonColapietro/suede-creator-skills

    Suede-owned pricing and packaging discipline. An agent skill from JasonColapietro/suede-creator-skills.

    127 GitHub stars~2.4k tokensUpdated today
    Sales & SupportAuto-check passed
  • Competitor Price Tracker

    OneWave-AI/claude-skills

    Monitor competitor pricing pages and send alerts when prices change.

    328 GitHub starsUsed in 2 repos~372 tokens
    Sales & SupportAuto-check passed
  • Deal Pricing

    jeremylongshore/tons-of-skills-marketplace

    Design pricing strategy and packaging — tiers, value metrics, enterprise pricing, freemium design, and pricing page copy.

    2.8k GitHub stars~1.2k tokensUpdated today
    Sales & SupportAuto-check: notes
  • Pricing Strategy

    borghei/Claude-Skills

    SaaS pricing design and optimization covering value metric selection, tier architecture, price point research, pricing page design, price increase execution, and competitive pricing analysis.

    886 GitHub stars~2k tokensUpdated 2 days ago
    Sales & SupportAuto-check passed

More from ericrisco/rsc-harness

All 233 skills in this repo
  • Ab Testing

    ericrisco/rsc-harness

    A skill your agent uses when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CUPED, or rescuing tests that won't go…

    174 GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed
  • Accessibility

    ericrisco/rsc-harness

    A skill your agent uses when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast…

    174 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed
  • Ads

    ericrisco/rsc-harness

    A skill your agent uses when running or fixing paid acquisition on Google or Meta — campaign structure (Performance Max, Demand Gen, Search, Advantage+), platform-fit creative, budget/scaling rules…

    174 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed
  • Agent Eval

    ericrisco/rsc-harness

    A skill your agent uses when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual…

    174 GitHub stars~3.2k tokensUpdated 2 days ago
    Auto-check passed
  • AI Media

    ericrisco/rsc-harness

    A skill your agent uses when a creative goal must become a finished media file: pick and order generative-media models per modality — AI voiceover, image-to-video clips, score — then glue them with…

    174 GitHub stars~3.3k tokensUpdated 2 days ago
    Auto-check passed
  • Analytics

    ericrisco/rsc-harness

    A skill your agent uses when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing.

    174 GitHub stars~2.8k tokensUpdated 2 days ago
    Auto-check passed

Works with

Questions about Pricing

What does Pricing do?

A skill your agent uses when setting or resetting what a product or service charges and how it is packaged — list price, margin floor, tiers, the value metric, the pricing model (flat, seat, usage…. Pricing is an agent skill from ericrisco/rsc-harness. Use when setting or resetting what a product or service charges and how it is packaged — list price, margin floor, tiers, the value metric, the pricing model (flat, seat, usage, outcome or hybrid), discount rules and purchasing-power localisation.

When should I use Pricing?

Pricing fits situations like: resetting what a product; service charges and how it is packaged — list price; the value metric; the pricing model (flat.

How do I install Pricing in Claude Code?

Run `npx skills add ericrisco/rsc-harness --skill pricing -a claude-code`. Or copy the skill folder (skills/pricing in ericrisco/rsc-harness) into .claude/skills/pricing in your project. Claude Code loads it when a task matches its description.

How do I install Pricing in Codex?

Run `npx skills add ericrisco/rsc-harness --skill pricing -a codex`. Or copy the skill folder (skills/pricing in ericrisco/rsc-harness) into .agents/skills/pricing in your project. Codex loads it when a task matches its description.

Can I use Pricing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ericrisco/rsc-harness --skill pricing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pricing, .gemini/skills/pricing, .github/skills/pricing and .opencode/skills/pricing in your project.

What does Pricing need to run?

Going by SKILL.md and its folder, Pricing needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Pricing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pricing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Pricing use?

Pricing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pricing use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Pricing?

Skills that share tags, products or a category with Pricing: Monetization (sickn33/agentic-awesome-skills, 47k stars), Pricing Strategy (OpenClaudia/openclaudia-skills, 713 stars), Suede Pricing (JasonColapietro/suede-creator-skills, 127 stars) and Competitor Price Tracker (OneWave-AI/claude-skills, 328 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pricing?

ericrisco (a GitHub user) maintains it in ericrisco/rsc-harness, which has 174 GitHub stars. The repository holds 233 skills in this directory. The repository was last updated on October 7, 2026.

Source: ericrisco/rsc-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.