Agent skill · Databases

agent-era-pricing

Redesign seat-based pricing for the agent era — when one human runs ten agents, per-seat models collapse. Use when agents are eroding seat counts, when asked to migrate to usage- or outcome-based pricing, to price an agent/API tier, or to defend revenue as customers automate their own usage. Produces a pricing migration plan: the new value metric, fences, agent-tier design, cannibalisation math, and a phased migration for existing customers. For general pricing and packaging strategy use pricing-strategy.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill agent-era-pricing --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/agent-era-pricing/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Agent Era Pricing Skill Seat pricing quietly assumed the user was a human who logs in. Agents break the assumption from both sides: your customers need fewer seats (one operator, ten agents), and your product gets *more* usage than ever. This skill redesigns the model around a value metric that survives non-human users — without torching existing revenue on the way. ## What This Skill Produces - A **value-metric decision**: what you charge for when seats stop proxying value - **Agent-tier design**: how agent/API usage is packaged, fenced, and priced - **Cannibalisation math**: what happens to current revenue under the new model, computed on real cohorts - A **phased migration plan** for existing customers, with the grandfathering decision made explicitly ## Required Inputs Ask for (if not already provided): - **Current model**: plans, price points, seat definitions, current API/automation pricing if any - **The evidence of pressure**: seat contraction, API traffic growth, customer asks, competitor moves - **Unit economics**: cost to serve a seat vs an API call/agent action (rough is fine, labelled) - **3-5 representative customer profiles** with seat counts and usage (the canniba

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Method
  4. Output Format
  5. Agent-Era Pricing Plan: [product]
  6. Quality Checks
  7. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the agent-era-pricing skill do?

Redesign seat-based pricing for the agent era — when one human runs ten agents, per-seat models collapse. Use when agents are eroding seat counts, when asked to migrate to usage- or outcome-based pricing, to price an agent/API tier, or to defend revenue as customers automate their own usage. Produces a pricing migration plan: the new value metric, fences, agent-tier design, cannibalisation math, and a phased migration for existing customers. For general pricing and packaging strategy use pricing-strategy.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill agent-era-pricing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going