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.
git clone --depth 1 https://github.com/lucasgaravelli/pm-skills-claude-codeWrote 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/commands/lucasgaravelli/pm-skills-claude-code/pricing)<a href="https://agentmods.dev/commands/lucasgaravelli/pm-skills-claude-code/pricing"><img src="https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/pricing.svg" alt="Measured on agentmods" 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.00000 | $0.04168 |
| Opus 5 | $0.00000 | $0.02084 |
| Sonnet 5 | $0.00000 | $0.00834 |
| Haiku 4.5 | $0.00000 | $0.00417 |
Grade A, and why
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 8d 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
100% identical to pricing — 0 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pricing
O que essa skill faz
Gera estrategia de pricing completa analisando 7 modelos de pricing, willingness-to-pay, estrutura de tiers, e plano de experimentacao. Baseado nos frameworks de Lenny Rachitsky e Phuryn.
Saida: Recomendacao de pricing com modelo escolhido, tiers desenhados, analise competitiva, e plano de testes.
Quando usar
- Lancando produto novo — precisa definir pricing inicial
- Revenue estagnada — pricing pode ser o problema
- Movendo upmarket ou downmarket — pricing precisa acompanhar
- Competitors mudaram pricing — precisa reposicionar
- Revisao semestral de pricing (todo produto deveria fazer)
Input esperado
Minimo:
- Produto: O que faz, para quem
- Valor entregue: Qual ROI o cliente recebe
- Estagio: Early (PMF seeking), growth, scale
- Modelo atual: Se ja tem pricing, qual e
Opcional:
- Dados de competitors (pricing publico)
- Dados de entrevistas sobre willingness-to-pay
- Revenue atual e targets
- Segmentos de cliente com tamanhos
- Custo de servir cada cliente
7 Modelos de Pricing
1. Flat-rate
Como funciona: Preco unico, tudo incluido. Exemplo: Basecamp ($99/mo, unlimited users) Melhor para: Produtos simples, mensagem clara, SMB Risco: Deixa dinheiro na mesa em enterprise. Nao escala com valor.
2. Per-seat
Como funciona: Cobra por usuario ativo. Exemplo: Slack ($8.75/user/mo), Figma ($15/editor/mo) Melhor para: Collaboration tools, produtos que escalam com team size Risco: Incentiva account sharing. Friction em times grandes.
3. Usage-based
Como funciona: Paga pelo que usa (API calls, storage, compute). Exemplo: AWS, Twilio ($0.0075/SMS), Stripe (2.9% + $0.30) Melhor para: Infra, APIs, produtos com uso variavel Risco: Revenue impredictivel. Cliente pode otimizar para gastar menos.
4. Tiered
Como funciona: 2-4 planos com features crescentes. Exemplo: Notion (Free/Plus/Business/Enterprise), Zoom (Free/Pro/Business) Melhor para: Maioria dos SaaS. Permite capturar valor de segmentos diferentes. Risco: Tier design errado = canibalização. Feature gating complexo.
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.
- 8d ago First seen · 439 lines · 0 tokens per session scan A 1dfff167a40e
pricing is a command published in the GitHub repository lucasgaravelli/pm-skills-claude-code (20 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,168 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pricing, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.