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 evgenii-studitskikh/Claude-Code-SaaS-Studio --skill design-pricinggit clone --depth 1 https://github.com/evgenii-studitskikh/Claude-Code-SaaS-StudioWrote 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/evgenii-studitskikh/claude-code-saas-studio/design-pricing)<a href="https://agentmods.dev/skills/evgenii-studitskikh/claude-code-saas-studio/design-pricing"><img src="https://agentmods.dev/badge/skills/evgenii-studitskikh/claude-code-saas-studio/design-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/evgenii-studitskikh/claude-code-saas-studio/design-pricing"><img src="https://agentmods.dev/badge/skills/evgenii-studitskikh/claude-code-saas-studio/design-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.00045 | $0.00576 |
| Opus 5 | $0.00023 | $0.00288 |
| Sonnet 5 | $0.00009 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
design-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 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 — 23 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design a pricing model that is both commercially sound and implementable with Stripe's product/price/subscription primitives. Non-autonomous: every tier, limit, and Stripe mapping is proposed and confirmed before being written to the spec.
Phases
- Load context — read
docs/specs/prd.mdfor the target user personas and success metrics, anddocs/specs/idea-validation.mdfor willingness-to-pay signals. If neither exists, ask the user to describe the intended audience and rough price sensitivity. - Propose tier structure — suggest 2–4 plan tiers (e.g., Free/Starter/Pro/Enterprise) with names, monthly and annual prices, and the key differentiating limits (seats, usage units, feature gates). Present the tiers as a comparison table. Ask the user to adjust before moving on.
- Define metered units and feature gates — for each tier, specify: which features are gated (boolean), which are metered (unit name, included allowance, overage price), and the upgrade trigger (what makes a user need the next tier). This informs which Stripe Price objects will be
recurringvs.metered. - Design upgrade/downgrade and trial rules — propose: trial length (days), trial-to-paid conversion behavior, proration strategy on plan changes, and what happens to data when a user downgrades below a current-usage limit. Get explicit sign-off on these rules — they have customer-experience implications.
- Map to Stripe objects — for each tier, define the Stripe Product name, Price ID naming convention (e.g.,
price_starter_monthly), billing interval, and any metered price configuration. Note that actual Stripe objects will be created in/setup-billing; this phase produces the spec only. - Write the spec — fill
.claude/templates/pricing.mdintodocs/specs/pricing.md. Underfullreview, present each section; underlean/solo, write after a single confirmation. Next step: point to/setup-billing.
Output
docs/specs/pricing.md — tier definitions, Stripe object mapping, and upgrade/downgrade rules. Writes nothing without approval.
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 · 23 lines · 45 tokens per session scan A cdcdbcbfe19d
design-pricing is a skill published in the GitHub repository evgenii-studitskikh/Claude-Code-SaaS-Studio (1 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 576 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-31.
Other skills, from other repositories
odoo-docker-deployment
Production-ready Docker and docker-compose setup for Odoo with PostgreSQL, persistent volumes, environment-based configuration, and Nginx reverse proxy.
odoo-inventory-optimizer
Expert guide for Odoo Inventory: stock valuation (FIFO/AVCO), reordering rules, putaway strategies, routes, and multi-warehouse configuration.
odoo-rpc-api
Expert on Odoo's external JSON-RPC and XML-RPC APIs. Covers authentication, model calls, record CRUD, and real-world integration examples in Python, JavaScript, and curl.
odoo-security-rules
Expert in Odoo access control: ir.model.access.csv, record rules (ir.rule), groups, and multi-company security patterns.
checkout
A Git command workflow for creating a new branch from the current repository changes and optional ticket or task context. Git is a tool for tracking code changes and branches are separate lines of work.
quality-and-returns
CIEL's framework for manufacturing quality (NCR/CAPA) and reverse logistics (Returns/Grading).