Agent skill

Pricing And Packaging

by cbrock84 in cbrock84/headcount

Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction.

MITAuto-check passed

Install Pricing And Packaging

skills CLI
$ npx skills add cbrock84/headcount --skill pricing-and-packaging -a claude-code

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

GitHub CLI
$ gh skill install cbrock84/headcount pricing-and-packaging --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/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/revenue/skills/pricing-and-packaging .claude/skills/pricing-and-packaging && 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-and-packaging
GitHub stars
2k
Token cost
~861 tokens
SKILL.md length
490 words
Files
2 (incl. references)
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction.

  • SKILL.md covers The pricing metric, Setting the level, Packaging and Monetization surfaces, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pricing And Packaging is an agent skill from cbrock84/headcount. Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing change is safe to make.

Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

Example prompts

  • “/pricing-and-packaging”

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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 And Packaging loads about 861 tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 91 tokens; SKILL.md has 490 words of instructions outside code blocks.

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 490 words, ~861 tokens.

Download SKILL.mdSave it as .claude/skills/pricing-and-packaging/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
pricing-and-packaging
description
Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing change is safe to make.

Pricing and packaging

The highest-leverage number in the business and the least examined. Most companies are underpriced and have never tested it.

The pricing metric

Choose what you charge per before choosing how much. It should scale with the value the customer receives, be predictable enough to budget, and be something they cannot easily game.

Get this wrong and no amount of tuning the number fixes it — a metric that scales with your cost rather than their value creates a permanent argument at every renewal.

Setting the level

Anchor on value delivered, not cost incurred. Cost sets a floor and nothing else.

Evidence to gather: what the alternative costs them today including labor, what similar categories charge, and what current customers say about price — with the caveat that nobody says a price is too low. Willingness-to-pay research is directional, not decisive; people misreport.

If nobody ever objects to your price, it is too low. Some loss on price is correct.

Packaging

Tiers should map to distinguishable segments with different needs, not to arbitrary feature counts. Three is usually right; more creates paralysis and support load.

Each tier needs one obvious reason to upgrade, tied to something that grows with the customer's success. Gating on a feature they will never need does not drive upgrades; gating on a limit they will hit does.

Name tiers for who they are for, not by metal. "Team" and "Business" tell a buyer where they belong.

Monetization surfaces

Upgrade prompts and paywalls should appear at the moment of blocked value — when someone is trying to do the thing the tier does not allow, not on a schedule.

Explain what is behind the gate and why the limit exists. An unexplained wall reads as extraction. Show the value already received before asking for payment, and make declining easy — dark patterns buy one conversion and lose the account.

Show full SKILL.md (179 more words)Show less

Changing price

  • Grandfather existing customers, or expect churn well beyond the price-sensitive segment.
  • Announce with real notice and a clear reason.
  • Change one thing at a time — price and packaging together makes the result unreadable.
  • Model the downside first: at what churn rate does this increase lose money?

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Change price without telling existing customers before it takes effect and honoring what they already signed.
  • Pick a pricing metric the customer cannot predict. If they cannot forecast the bill, they will not sign.
  • Add a tier to close a single deal. Tiers are a permanent tax on every conversation after it.
  • Discount without taking something back in exchange — term, scope, payment timing, a reference. A free discount resets the price for everyone.

© cbrock84, 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 1 other file (references) in plugins/revenue/skills/pricing-and-packaging of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Pricing And Packaging 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 And Packaging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pricing And Packaging this skillcbrock84/headcount2k—~861Automated safety check: PassMIT
Pricing Packaging Planneraaron-he-zhu/aaron-marketing-skills2.9k—~3.3kAutomated safety check: PassApache-2.0
Pricingsickn33/agentic-awesome-skills47k1 repos~1.9kAutomated safety check: PassMIT
Design Systemaffaan-m/ECC276k—~698Automated safety check: PassMIT
Design Guidepaperclipai/paperclip99k1 repos~3.1kAutomated safety check: PassMIT
Pricing Strategyalirezarezvani/claude-skills28k1 repos~3.5kAutomated safety check: PassMIT

Similar skills

  • Pricing Packaging Planner

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "plan launch pricing", "design pricing tiers / packaging", or "set up a launch discount / early-bird offer"; produces a launch pricing and packaging…

    2.9k GitHub stars~3.3k tokensUpdated today
    Writing & ContentAuto-check passed
  • Pricing

    sickn33/agentic-awesome-skills

    When the user wants help with pricing decisions, packaging, or monetization strategy.

    47k GitHub starsUsed in 1 repo~1.9k tokens
    Sales & SupportAuto-check passed
  • Design System

    affaan-m/ECC

    Generate a design system from an existing codebase or audit one for visual consistency: extract tokens (colors, typography, spacing, shadows) into design-tokens.json and CSS custom properties with…

    276k GitHub stars~698 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Design Guide

    paperclipai/paperclip

    Paperclip UI design system guide for building consistent, reusable frontend components.

    99k GitHub starsUsed in 1 repo~3.1k tokens
    Frontend & DesignAuto-check passed
  • Pricing Strategy

    alirezarezvani/claude-skills

    Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy.

    28k GitHub starsUsed in 1 repo~3.5k tokens
    Sales & SupportAuto-check passed
  • Audits a design against Dieter Rams' ten principles of good design, scores each with evidence, and hands off a make-plan prompt for a new, refined or redesigned outcome.

    99k GitHub stars~4.6k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

More from cbrock84/headcount

All 178 skills in this repo
  • Agent Hierarchy

    cbrock84/headcount

    Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…

    2k GitHub stars~1.2k tokensUpdated 22 days ago
    Auto-check passed
  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 22 days ago
    Auto-check passed
  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 22 days ago
    Auto-check passed
  • Activation

    cbrock84/headcount

    Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.

    2k GitHub stars~865 tokensUpdated 22 days ago
    Auto-check passed
  • AI ML Governance

    cbrock84/headcount

    Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.

    2k GitHub stars~1k tokensUpdated 22 days ago
    Auto-check passed
  • AI Research Analyst

    cbrock84/headcount

    Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.

    2k GitHub stars~916 tokensUpdated 22 days ago
    Auto-check passed

Questions about Pricing And Packaging

What does Pricing And Packaging do?

Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Pricing And Packaging is an agent skill from cbrock84/headcount. Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction.

How do I install Pricing And Packaging in Claude Code?

Run `npx skills add cbrock84/headcount --skill pricing-and-packaging -a claude-code`. Or copy the skill folder (plugins/revenue/skills/pricing-and-packaging in cbrock84/headcount) into .claude/skills/pricing-and-packaging in your project. Claude Code loads it when a task matches its description.

How do I install Pricing And Packaging in Codex?

Run `npx skills add cbrock84/headcount --skill pricing-and-packaging -a codex`. Or copy the skill folder (plugins/revenue/skills/pricing-and-packaging in cbrock84/headcount) into .agents/skills/pricing-and-packaging in your project. Codex loads it when a task matches its description.

Can I use Pricing And Packaging 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 cbrock84/headcount --skill pricing-and-packaging -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-and-packaging, .gemini/skills/pricing-and-packaging, .github/skills/pricing-and-packaging and .opencode/skills/pricing-and-packaging in your project.

What does Pricing And Packaging need to run?

SKILL.md names no scripts, command-line tools or credentials: Pricing And Packaging is instructions for the agent only.

Does Pricing And Packaging 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 And Packaging 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. Review the folder before installing.

What licence does Pricing And Packaging use?

Pricing And Packaging 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 And Packaging use?

About 861 tokens (SKILL.md is roughly 3.4k 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 698 tokens, read only when the agent opens those files.

What are the alternatives to Pricing And Packaging?

Skills that share tags, products or a category with Pricing And Packaging: Pricing Packaging Planner (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Pricing (sickn33/agentic-awesome-skills, 47k stars), Design System (affaan-m/ECC, 276k stars) and Design Guide (paperclipai/paperclip, 99k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pricing And Packaging?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.

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