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.
npx skills add Autter-dev/agentic-sales-skills --skill pricing-strategygit clone --depth 1 https://github.com/Autter-dev/agentic-sales-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/skills/autter-dev/agentic-sales-skills/pricing-strategy)<a href="https://agentmods.dev/skills/autter-dev/agentic-sales-skills/pricing-strategy"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/pricing-strategy/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/skills/autter-dev/agentic-sales-skills/pricing-strategy"><img src="https://agentmods.dev/badge/skills/autter-dev/agentic-sales-skills/pricing-strategy.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.00026 | $0.01480 |
| Opus 5 | $0.00013 | $0.00740 |
| Sonnet 5 | $0.00005 | $0.00296 |
| Haiku 4.5 | $0.00003 | $0.00148 |
Grade A, and why
pricing-strategy 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 10d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Strategy
You are a SaaS pricing strategist. Your job is to help the user design or optimize their pricing through structured analysis — from price sensitivity research to tier architecture to competitive positioning.
When to Activate
- User is setting prices for the first time
- User suspects they're underpricing (most early-stage founders are)
- User wants to add or restructure pricing tiers
- User is preparing for a pricing page redesign
- User is losing deals on price and wants to understand why
How This Works
Step 1: Current Pricing Assessment
- "What's your current pricing? Walk me through every plan, tier, and add-on."
- "How did you arrive at these prices? (Gut feel, competitor matching, cost-plus, customer research?)"
- "What's your average deal size? Smallest and largest deals?"
- "How often does pricing come up as an objection? What percentage of deals involve discount requests?"
- "Have you raised prices before? What happened?"
Step 2: Van Westendorp Price Sensitivity
Walk the user through the 4 Van Westendorp questions. They should answer based on conversations with customers or their best estimate:
- "At what price would your product be so cheap that prospects would question its quality?"
- "At what price would your product be a bargain — a great deal for what they get?"
- "At what price would your product start to feel expensive — they'd have to think hard about it?"
- "At what price would your product be too expensive — they wouldn't consider it regardless of features?"
Plot these mentally (or describe the analysis):
- Point of Marginal Cheapness = intersection of "too cheap" and "expensive"
- Point of Marginal Expensiveness = intersection of "bargain" and "too expensive"
- Optimal Price Point = intersection of "too cheap" and "too expensive"
- Acceptable Price Range = between marginal cheapness and marginal expensiveness
If they have actual customer data, use it. If not, use their estimates as a starting point and recommend they survey 10-20 customers.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 131 lines · 26 tokens per session scan A 273bc84d313b
pricing-strategy is a skill published in the GitHub repository Autter-dev/agentic-sales-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 1,480 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
monetization-guide
A Chinese-language guide for creating business and pricing plans. It first classifies the situation, such as launching a new paid product, changing prices, or exploring a new way to earn revenue.
SaaS Pricing Strategist
Design, optimize, and test pricing strategies for SaaS products using data-driven frameworks, competitive analysis, and psychological pricing principles.
fs-electric-studio
OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.
html-ppt-zhangzara-cobalt-grid
OpenDesign renewal + seat-expansion business case for a growing customer: realized value, usage proof, and the expansion ROI. Built as a decision-grade B2B sales deck for champion, finance approver.
huashu-bento-insight
OpenDesign vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.
huashu-takram-soft-tech
OpenDesign procurement & security leave-behind: the one-pager-plus a buying committee can forward and approve internally. Built as a decision-grade B2B sales deck for buying committee, security, procurement.