Chatbot
majiayu000/claude-skill-registry
A skill your agent uses when a support or sales bot on a live website must behave: persona/system prompt, grounding so it cannot invent prices or policy, jailbreak and injection defense, the human…
Design a usage-based pricing scheme that scales revenue with value without scaring customers away — the metric that tracks value, tiers with included volume, and the guardrails that prevent bill…
Install Usage Based Pricing Model
$ npx skills add mohitagw15856/pm-claude-skills --skill usage-based-pricing-model -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills usage-based-pricing-model --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/usage-based-pricing-model .claude/skills/usage-based-pricing-model && rm -rf skills-srcUse ~/.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/
Install the "usage-based-pricing-model" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/usage-based-pricing-model into .claude/skills/usage-based-pricing-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usage-based-pricing-model", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/usage-based-pricing-modelType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill usage-based-pricing-model -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills usage-based-pricing-model --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/usage-based-pricing-model .agents/skills/usage-based-pricing-model && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "usage-based-pricing-model" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/usage-based-pricing-model into .agents/skills/usage-based-pricing-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usage-based-pricing-model", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill usage-based-pricing-model -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills usage-based-pricing-model --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/usage-based-pricing-model .cursor/skills/usage-based-pricing-model && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "usage-based-pricing-model" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/usage-based-pricing-model into .cursor/skills/usage-based-pricing-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usage-based-pricing-model", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/usage-based-pricing-model--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill usage-based-pricing-model -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills usage-based-pricing-model --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/usage-based-pricing-model .gemini/skills/usage-based-pricing-model && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "usage-based-pricing-model" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/usage-based-pricing-model into .gemini/skills/usage-based-pricing-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usage-based-pricing-model", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills usage-based-pricing-modelInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill usage-based-pricing-model -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/usage-based-pricing-model .github/skills/usage-based-pricing-model && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "usage-based-pricing-model" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/usage-based-pricing-model into .github/skills/usage-based-pricing-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usage-based-pricing-model", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill usage-based-pricing-model -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills usage-based-pricing-model --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/usage-based-pricing-model .opencode/skills/usage-based-pricing-model && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "usage-based-pricing-model" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/usage-based-pricing-model into .opencode/skills/usage-based-pricing-model/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usage-based-pricing-model", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
usage-based-pricing-model- GitHub stars
- 1.4k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 1,036 words
- Files
- 1
- Skills in repo
- 1,322
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design a usage-based pricing scheme that scales revenue with value without scaring customers away — the metric that tracks value, tiers with included volume, and the guardrails that prevent bill…
- Works in 7 steps: Choose the metric against four tests.… → Anchor with a platform fee. A flat base… → Set tiers on the real distribution.… → …
- Asked to design usage-based
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Metric, Tiers,… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Usage Based Pricing Model is an agent skill from mohitagw15856/pm-claude-skills. Design a usage-based pricing scheme that scales revenue with value without scaring customers away — the metric that tracks value, tiers with included volume, and the guardrails that prevent bill shock. Use when asked to design usage-based or metered pricing, move from seats to consumption, price an API or AI product per unit, or handle customers afraid of variable bills. Produces the value-metric selection, the tier structure with included volumes and overage rates, the bill-shock guardrails, revenue modelling at…
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering, covering Pricing strategy and LLM guardrails. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to design usage-based
- Metered pricing
- Move from seats to consumption
- AI product per unit
Example prompts
- “/usage-based-pricing-model”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Choose the metric against four tests. (a) It rises when the customer gets more value; (b) the customer can predict and control it; (c) you…
- Anchor with a platform fee. A flat base with included volume stabilises your revenue and their budget. Pure per-unit pricing makes every…
- Set tiers on the real distribution. Included volumes sit at natural breakpoints in the usage percentiles — not round numbers. The tier a…
- Price overage as a bridge, not a fine. Overage slightly above the effective in-tier rate nudges upgrades; overage at multiples of it reads…
- Build the guardrails before launch. Spend alerts at thresholds the customer sets, a soft cap or auto-upgrade at tier boundaries…
- Model revenue at the percentiles. Run the proposed scheme against P10/P50/P90 usage. Average-based modelling hides that the top decile…
- Check the degenerate cases. The customer at 100× median usage, the one at near-zero, the one whose usage spikes 20× for one day. Decide…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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
Usage Based Pricing Model loads about 1.9k tokens when it runs. Until then it costs about 153 tokens; SKILL.md has 1,036 words of instructions outside code blocks.
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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 1,036 words, ~1,926 tokens.
Download SKILL.mdSave it as
.claude/skills/usage-based-pricing-model/SKILL.md (or your agent's skills folder).- name
- usage-based-pricing-model
- description
- Design a usage-based pricing scheme that scales revenue with value without scaring customers away — the metric that tracks value, tiers with included volume, and the guardrails that prevent bill shock. Use when asked to design usage-based or metered pricing, move from seats to consumption, price an API or AI product per unit, or handle customers afraid of variable bills. Produces the value-metric selection, the tier structure with included volumes and overage rates, the bill-shock guardrails, revenue modelling at usage percentiles, and the migration plan from the current model.
Usage-Based Pricing Model
Usage pricing done right means revenue grows when the customer's value grows. Done wrong it means a customer opens an invoice ten times last month's, screenshots it, and churns publicly. The difference is rarely the rate — it is whether the metric tracks value the customer recognises, and whether the guardrails make the worst-case bill survivable. This designs both, and models the revenue before you commit.
What This Skill Produces
- The value-metric decision — the unit you charge for, tested against the four criteria that separate a good meter from a resented one
- The tier structure — included volumes, overage rates, and the flat platform fee that stabilises revenue
- Bill-shock guardrails — caps, alerts, forgiveness policies, and the commit-and-drawdown option for predictability-hungry buyers
- Revenue modelling — projected revenue at the P10/P50/P90 of the actual usage distribution, not at the average
- The degenerate-case check — who wins and who loses at the extremes of the usage curve, before a customer finds out for you
- A migration plan — how existing customers move from the current model without a revolt
Required Inputs
Ask for these if not provided:
- The product and what "usage" means in it — API calls, seats, tokens, GB, transactions, jobs, minutes
- The usage distribution — real percentiles across current customers if they exist (P10/P50/P90/P99), or honest estimates
- The cost structure — marginal cost per unit of usage, so the floor is known
- The current model and its problem — what pricing exists today and what is breaking (leaving money on big accounts, scaring small ones, misaligned with value)
- The buyer — who approves the bill, and how much variance their budget process tolerates
Framework: Metric, Tiers, Guardrails, Model
- Choose the metric against four tests. (a) It rises when the customer gets more value; (b) the customer can predict and control it; (c) you can meter it accurately and explain the meter; (d) it does not punish behaviour you want (charging per user punishes adoption; charging per API call punishes integration depth). Most usage-pricing failures are metric failures, not rate failures.
- Anchor with a platform fee. A flat base with included volume stabilises your revenue and their budget. Pure per-unit pricing makes every invoice a re-decision.
- Set tiers on the real distribution. Included volumes sit at natural breakpoints in the usage percentiles — not round numbers. The tier a customer lands in should feel like a description of them, not a trap.
- Price overage as a bridge, not a fine. Overage slightly above the effective in-tier rate nudges upgrades; overage at multiples of it reads as punishment and produces the screenshot.
- Build the guardrails before launch. Spend alerts at thresholds the customer sets, a soft cap or auto-upgrade at tier boundaries, first-incident forgiveness for a runaway bill, and an annual commit-with-drawdown for buyers who need a fixed number. The guardrails are the product's answer to "what's the worst that happens?" — have one.
- Model revenue at the percentiles. Run the proposed scheme against P10/P50/P90 usage. Average-based modelling hides that the top decile funds everything and the bottom quartile may cost more to bill than it pays.
- Check the degenerate cases. The customer at 100× median usage, the one at near-zero, the one whose usage spikes 20× for one day. Decide the policy for each now, in writing.
Output Format
Show full SKILL.md (490 more words)Show less
Usage pricing model: [product] · [date] · v[n]
Value metric: [unit] · Why: [the four tests, answered in one line each] Rejected metrics: [alternative — which test it failed]
Tier structure
| Tier | Platform fee | Included volume | Overage rate | Lands who |
|---|---|---|---|---|
| [name] | [amount]/mo | [n units] | [rate]/unit | [the percentile band this describes] |
Effective rate curve: at P10 usage [rate/unit] · P50 [rate] · P90 [rate] — [flag any point where a heavier user pays a higher effective rate, which inverts the volume expectation]
Guardrails
- Alerts: [customer-set thresholds, default on at n% of included volume]
- Cap behaviour: [hard stop / soft cap with auto-upgrade / uncapped with alert]
- Forgiveness: [first-incident policy for runaway usage, stated before it happens]
- Predictability option: [annual commit with drawdown / fixed tier with true-up]
Revenue model
| Scenario | Customers | Revenue/mo | vs current model |
|---|---|---|---|
| P10 usage | |||
| P50 usage | |||
| P90 usage | |||
| Margin floor: marginal cost [x]/unit against lowest effective rate [y]/unit → [safe / underwater at tier n] |
Degenerate cases: [100× median: policy] · [near-zero: policy] · [20× one-day spike: policy]
Migration: [grandfathering window · mapping from old plans · the message, led by who gets cheaper] · Expected revolt risk: [which segment pays more, by how much, and the offer that softens it]
Quality Checks
- The metric passes all four tests, and rejected alternatives are recorded with the failing test
- Tiers are placed on the real usage distribution, not round numbers
- The effective rate falls (or holds) as usage grows — no inversion where heavy users pay more per unit
- Every guardrail exists in the design before launch, not as a support policy invented after the first incident
- Revenue is modelled at percentiles, with the current model as the comparison column
- The margin floor is checked against the lowest effective rate
- The three degenerate cases have written policies
- The migration names who pays more and what they are offered
Anti-Patterns
- Choosing the meterable metric over the valuable one. You can meter API calls precisely; if value lives in outcomes, the customer resents every call.
- Pricing on the average customer. The usage distribution is heavy-tailed; the average customer barely exists.
- Overage as a fine. Overage at 5× the in-tier rate produces the invoice screenshot that becomes your pricing page's reputation.
- No answer to "what's the worst case?" A buyer who cannot bound the bill will not sign, and the one who does not ask will churn when it happens.
- Punishing adoption. Per-seat metering on a collaboration product taxes the behaviour that retains the account.
- Launching without the forgiveness policy. The first runaway bill is a certainty; deciding the response during the incident guarantees it goes badly.
- Migrating everyone at once with a price rise buried inside. The model change takes the blame for the increase, and both die together.
Example Trigger Phrases
- "Design usage-based pricing for our API"
- "We want to move from per-seat to consumption pricing"
- "How do we price our AI product per token without bill shock?"
- "Customers are afraid of variable bills — what guardrails do we need?"
- "Model what usage pricing would do to our revenue"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/usage-based-pricing-model of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Usage Based Pricing Model 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Usage Based Pricing Model this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Chatbotmajiayu000/claude-skill-registry | 666 | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Add Model Pricelangfuse/langfuse | 36k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| ObliteratusRedWoodOG/Hermes-Desktop | 177 | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Lemonade Router Builderamd/skills | 398 | — | ~4k | Automated safety check: Pass | MIT | |
| Wp Project Triagegambitph/Stackable | 350 | 4 repos | ~371 | Automated safety check: Pass | GPL-3.0 |
Similar skills
Add Model Price
langfuse/langfuse
A skill your agent uses when editing worker/src/constants/default-model-prices.json, packages/shared/src/server/llm/types.ts, pricing tiers, tokenizer IDs, or matchPattern regexes for OpenAI…
Obliteratus
RedWoodOG/Hermes-Desktop
Remove refusal behaviors from open-weight LLMs using OBLITERATUS — mechanistic interpretability techniques (diff-in-means, SVD, whitened SVD, LEACE, SAE decomposition, etc.) to excise guardrails…
Lemonade Router Builder
amd/skills
Turns a natural-language description of routing intent into a valid Lemonade collection.router policy JSON.
Wp Project Triage
gambitph/Stackable
A skill your agent uses when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a…
Aisafetyhot
wuyoscar/AISafetyHot-Hub
Read AI Safety HOT daily digests, search recent AI safety research and incidents, and follow current hot topics.
More from mohitagw15856/pm-claude-skills
All 1,322 skills in this repoExit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Offer Comparison
mohitagw15856/pm-claude-skills
Compare two or more job offers as total-comp curves over four years — vesting cliffs, bonuses, 401(k) match, and the crossover year computed, not vibed.
Refinance Breakeven
mohitagw15856/pm-claude-skills
Compute the month a refinance actually starts saving money — payment delta, breakeven month, and total interest on both paths including the term-reset trap.
Rent Vs Buy
mohitagw15856/pm-claude-skills
Model rent-vs-buy honestly — year-by-year net position for both paths including the assumption everyone drops (the renter invests the difference), with a breakeven horizon instead of a verdict.
Related
Categories
Questions about Usage Based Pricing Model
What does Usage Based Pricing Model do?
Design a usage-based pricing scheme that scales revenue with value without scaring customers away — the metric that tracks value, tiers with included volume, and the guardrails that prevent bill…. Usage Based Pricing Model is an agent skill from mohitagw15856/pm-claude-skills. Design a usage-based pricing scheme that scales revenue with value without scaring customers away — the metric that tracks value, tiers with included volume, and the guardrails that prevent bill shock.
When should I use Usage Based Pricing Model?
Usage Based Pricing Model fits situations like: asked to design usage-based; metered pricing; move from seats to consumption; AI product per unit.
How do I install Usage Based Pricing Model in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill usage-based-pricing-model -a claude-code`. Or copy the skill folder (skills/usage-based-pricing-model in mohitagw15856/pm-claude-skills) into .claude/skills/usage-based-pricing-model in your project. Claude Code loads it when a task matches its description.
How do I install Usage Based Pricing Model in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill usage-based-pricing-model -a codex`. Or copy the skill folder (skills/usage-based-pricing-model in mohitagw15856/pm-claude-skills) into .agents/skills/usage-based-pricing-model in your project. Codex loads it when a task matches its description.
Can I use Usage Based Pricing Model 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 mohitagw15856/pm-claude-skills --skill usage-based-pricing-model -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/usage-based-pricing-model, .gemini/skills/usage-based-pricing-model, .github/skills/usage-based-pricing-model and .opencode/skills/usage-based-pricing-model in your project.
What does Usage Based Pricing Model need to run?
SKILL.md names no scripts, command-line tools or credentials: Usage Based Pricing Model is instructions for the agent only.
Does Usage Based Pricing Model 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 Usage Based Pricing Model 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 Usage Based Pricing Model use?
Usage Based Pricing Model 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 Usage Based Pricing Model use?
About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Usage Based Pricing Model?
Skills that share tags, products or a category with Usage Based Pricing Model: Chatbot (majiayu000/claude-skill-registry, 666 stars), Add Model Price (langfuse/langfuse, 36k stars), Obliteratus (RedWoodOG/Hermes-Desktop, 177 stars) and Lemonade Router Builder (amd/skills, 398 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Usage Based Pricing Model?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,431 GitHub stars. The repository holds 1,322 skills in this directory. The repository was last updated on October 7, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.