PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.
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.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skillsWrote 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.
[](https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/agent-era-pricing)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/agent-era-pricing"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/agent-era-pricing/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.
<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/agent-era-pricing"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/agent-era-pricing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00103 | $0.01258 |
| Opus 5 | $0.00051 | $0.00629 |
| Sonnet 5 | $0.00021 | $0.00252 |
| Haiku 4.5 | $0.00010 | $0.00126 |
Grade A, and why
agent-era-pricing 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 cannibalisation test set)
Method
- Find the value metric that survives agents. Test candidates against three questions: does it scale with the value the customer receives (not your costs)? · is it counted identically whether a human or agent drives it? · can the customer predict their bill? Strong candidates are usually outcomes or work-objects (invoices processed, tickets resolved, campaigns run, records enriched) — not raw API calls (unpredictable, punishes retries) and not seats (dying assumption).
- Price the human and the agent differently, deliberately. The durable pattern is a hybrid: a platform/human layer (flat or few-seats — access, admin, support) plus a work layer priced on the value metric, agnostic to who did the work. Decide where agents authenticate: agent traffic on a user's token counted as that user's work, not as a "seat".
- Design the fences. What separates tiers now that seats don't: volume bands on the value metric, rate/concurrency limits, SSO/audit/compliance (still human-org fences), model/automation quality tiers. Every fence must be measurable and hard to game — name the gaming vector for each and why it's acceptable.
- Run the cannibalisation math on real cohorts. For each customer profile: current annual price vs new-model price at current usage, at 2× automation, at 5×. Sum to a revenue bridge. If the new model loses money on your best cohort, the metric or the bands are wrong — fix the model, don't hide the row.
- Phase the migration. New customers first (cleanest signal) → opt-in for existing (with a calculator showing their number) → forced migration only with long notice and a cap ("no more than X% increase in year one"). Grandfathering is a decision with a cost, not a default: state what perpetual legacy plans cost in five years.
- Set the tripwires. Which metrics reprice this model: value-metric inflation/deflation, gaming detected, agent share of traffic crossing thresholds. Pricing in the agent era is a program, not a project.
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.
- 8d ago First seen · 72 lines · 103 tokens per session scan A 5d90bf8345f9
agent-era-pricing is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,352 stars, last pushed 3d ago), licensed MIT. It adds 103 tokens to every session and 1,258 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.