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 OneWave-AI/claude-skills --skill pricing-strategygit clone --depth 1 https://github.com/OneWave-AI/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/skills/onewave-ai/claude-skills/pricing-strategy)<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/pricing-strategy"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-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/onewave-ai/claude-skills/pricing-strategy"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/pricing-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00077 | $0.00636 |
| Opus 5 | $0.00039 | $0.00318 |
| Sonnet 5 | $0.00015 | $0.00127 |
| Haiku 4.5 | $0.00008 | $0.00064 |
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 9d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Strategy Designer
Design data-driven pricing strategies that maximize revenue, align with market positioning, and scale with the business across B2B SaaS, consumer products, services, marketplaces, and physical goods.
Contents
references/required-inputs.md-- Inputs to gather before starting (product, market, competition, business context).references/analysis-framework.md-- The five pricing models to evaluate (cost-plus, value-based, competitor-based, penetration, premium).references/output-template.md-- Fullpricing-strategy.mdstructure to populate.references/best-practices.md-- Best practices, trigger phrases, and a worked example.
Workflow
-
Gather inputs. Collect product, cost, market, and competitor information. See
references/required-inputs.md. If anything is missing, ask before proceeding. -
Research competitors. Use WebSearch and WebFetch to find current competitor pricing. Look for official pricing pages (search "[competitor] pricing"), G2/Capterra/TrustRadius comparisons, recent blog posts or press releases about pricing changes, and Crunchbase for funding and growth signals.
-
Analyze the market. Determine where the product sits in the competitive landscape using market reports, analyst commentary, and customer reviews that mention pricing.
-
Build the cost model. Fill in the cost structure with the user. When exact numbers are unavailable, use industry benchmarks and note the assumptions.
-
Evaluate all five pricing models. Score each model against the specific product and market context using the framework in
references/analysis-framework.md. Do not skip a model; even when one is obviously wrong, explain why. -
Design the tier structure. Create tiers that align with customer segments, create natural upgrade paths, and maximize expansion revenue.
-
Model the financials. Project revenue, churn, expansion, and cash flow under multiple scenarios.
-
Write the strategy document. Generate the full
pricing-strategy.mdfollowingreferences/output-template.md. Use real numbers from the research, not placeholders.
What ships with it
4 files 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.
- 9d ago First seen · 45 lines · 77 tokens per session scan A f59959df4256
pricing-strategy is a skill published in the GitHub repository OneWave-AI/claude-skills (291 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 636 once invoked, about $0.0004 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 skills, from other repositories
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
incident-response
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
agb-begriff-vorformuliert-305
Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.