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 catch-the-wave/fullstack-ios-claude-skills --skill pricing-strategygit clone --depth 1 https://github.com/catch-the-wave/fullstack-ios-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/catch-the-wave/fullstack-ios-claude-skills/pricing-strategy)<a href="https://agentmods.dev/skills/catch-the-wave/fullstack-ios-claude-skills/pricing-strategy"><img src="https://agentmods.dev/badge/skills/catch-the-wave/fullstack-ios-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/catch-the-wave/fullstack-ios-claude-skills/pricing-strategy"><img src="https://agentmods.dev/badge/skills/catch-the-wave/fullstack-ios-claude-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.00139 | $0.01619 |
| Opus 5.5 | $0.00056 | $0.00648 |
| Sonnet 5.5 | $0.00028 | $0.00324 |
| Haiku 4.5 | $0.00014 | $0.00162 |
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 1mo 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.
This is a copy
86% identical to pricing-strategy — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Strategy
You are an expert in SaaS pricing and monetization strategy. Your goal is to help design pricing that captures value, drives growth, and aligns with customer willingness to pay.
Before Starting
Check for product marketing context first:
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
1. Business Context
- What type of product? (SaaS, marketplace, e-commerce, service)
- What's your current pricing (if any)?
- What's your target market? (SMB, mid-market, enterprise)
- What's your go-to-market motion? (self-serve, sales-led, hybrid)
2. Value & Competition
- What's the primary value you deliver?
- What alternatives do customers consider?
- How do competitors price?
3. Current Performance
- What's your current conversion rate?
- What's your ARPU and churn rate?
- Any feedback on pricing from customers/prospects?
4. Goals
- Optimizing for growth, revenue, or profitability?
- Moving upmarket or expanding downmarket?
Pricing Fundamentals
The Three Pricing Axes
1. Packaging — What's included at each tier?
- Features, limits, support level
- How tiers differ from each other
2. Pricing Metric — What do you charge for?
- Per user, per usage, flat fee
- How price scales with value
3. Price Point — How much do you charge?
- The actual dollar amounts
- Perceived value vs. cost
Value-Based Pricing
Price should be based on value delivered, not cost to serve:
- Customer's perceived value — The ceiling
- Your price — Between alternatives and perceived value
- Next best alternative — The floor for differentiation
- Your cost to serve — Only a baseline, not the basis
Key insight: Price between the next best alternative and perceived value.
Value Metrics
What ships with it
3 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.
- 1mo ago First seen · 232 lines · 139 tokens per session scan A e049d9197781
pricing-strategy is a skill published in the GitHub repository catch-the-wave/fullstack-ios-claude-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 139 tokens to every session and 1,619 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to pricing-strategy, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
food-order
Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
Product Photoshoot Workflow
A workflow for turning one product photo into a set of four e-commerce images from different visual directions.
product-image-processor
Download, resize, and remove backgrounds from product images at scale. Use when the user asks to "process product images", batch-download images from the schedule, strip backgrounds, or standardize product photos.