Borrowing it
Nothing to install: this file belongs to LeanOS-Technologies/strategy-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LeanOS-Technologies/strategy-os/main/.claude/skills/stg-designing-pricing/SKILL.mdgit clone --depth 1 https://github.com/LeanOS-Technologies/strategy-osWrote 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/leanos-technologies/strategy-os/stg-designing-pricing)<a href="https://agentmods.dev/skills/leanos-technologies/strategy-os/stg-designing-pricing"><img src="https://agentmods.dev/badge/skills/leanos-technologies/strategy-os/stg-designing-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/skills/leanos-technologies/strategy-os/stg-designing-pricing"><img src="https://agentmods.dev/badge/skills/leanos-technologies/strategy-os/stg-designing-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.00035 | $0.01535 |
| Opus 5 | $0.00017 | $0.00767 |
| Sonnet 5 | $0.00007 | $0.00307 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
stg-designing-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 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Design
Develop pricing hypothesis using value-based methodology. All WTP estimates are T3 (always). Prices are ranges, not points. Channel economics integrated.
Procedure
Step 1: Calculate Value Anchor [S]
Read: problem hypothesis (quantified cost of the problem).
Value = problem cost x percentage resolved by solution. Price ceiling = value x capture rate (10-25% for SaaS).
Present as range. Label T2 (derived from problem cost estimate which may itself be T2).
Produce: value anchor range [T2].
Gate: value_anchor_calculated: bool -- derived from quantified problem cost, not asserted.
- Pass: Step 2.
- Fail: If problem cost is not quantified, estimate from severity score and segment characteristics. Note increased uncertainty (T2-T3).
Step 2: Analyze Competitive Pricing [S]
Read: competitor profiles from stg-analyzing-competition.
Map competitor pricing:
- Tiers and price points (from pricing pages)
- Packaging model (per-seat, usage, flat)
- Free tier availability and limits
Identify price gaps (underserved price ranges).
Produce: competitive pricing map [T1] + gap analysis [T2].
Gate: competitive_pricing_mapped: bool -- at least 2 competitors' pricing documented with source URLs.
- Pass: Step 3.
- Fail: If competitor pricing is hidden (enterprise "contact us"), note as data gap. Use available benchmarks for the category.
Step 3: Select Revenue Model [R]
Match revenue model to growth architecture:
| Growth Architecture | Revenue Model | Rationale |
|---|---|---|
| PLG | Freemium or usage-based with paid conversion | Users must experience value before paying |
| Network | Free tier with network-gated premium | Network value increases with users; premium unlocks at density |
| Traditional | Subscription (monthly/annual) | Sales-assisted, predictable revenue |
| Hybrid | Base subscription + usage overage | Predictable base with upside from usage |
Mode overlay:
- BOOTSTRAP: biases toward immediate revenue (no extended free tiers)
- VENTURE: can sustain longer free periods if growth loop is strong
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 · 153 lines · 35 tokens per session scan A c3b420337e51
stg-designing-pricing is a skill published in the GitHub repository LeanOS-Technologies/strategy-os (37 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 1,535 once invoked, about $0.0002 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-30.
Other skills, from other repositories
email-sequence
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle…
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
guidance
Control LLM output with regex and grammars, guarantee valid JSON/XML/code generation, enforce structured formats, and build multi-step workflows with Guidance - Microsoft Research's constrained generation framework.
content-research-writer
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
training-llms-megatron
Trains large language models (2B-462B parameters) using NVIDIA Megatron-Core with advanced parallelism strategies. Use when training models >1B parameters, need maximum GPU efficiency (47% MFU on H100), or require tensor/pipeline/sequence/context/expert parallelism. Production-ready framework used for Nemotron, LLaMA…