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/measure-pmf)<a href="https://agentmods.dev/commands/lucasgaravelli/pm-skills-claude-code/measure-pmf"><img src="https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/measure-pmf/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/commands/lucasgaravelli/pm-skills-claude-code/measure-pmf"><img src="https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/measure-pmf.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.00000 | $0.02616 |
| Opus 5 | $0.00000 | $0.01308 |
| Sonnet 5 | $0.00000 | $0.00523 |
| Haiku 4.5 | $0.00000 | $0.00262 |
Grade A, and why
measure-pmf 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.
This is a copy
100% identical to measure-pmf — 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/measure-pmf
O que essa skill faz
Avalia o grau de Product-Market Fit do seu produto usando frameworks quantitativos e qualitativos consolidados por 46 líderes de produto. Baseado no Sean Ellis Test, Superhuman PMF Engine e métricas de retenção.
Saída: PMF Assessment Report com score, estágio, evidências e plano de ação.
Quando usar
- Após launch: "será que temos PMF?"
- Antes de escalar: validar se é hora de investir em growth
- Quando métricas estão ambíguas (crescimento + churn alto)
- Para convencer stakeholders com dados, não intuição
- Revisão periódica (PMF pode ser perdido)
- Antes de fundraising: provar tração
Input esperado
Mínimo:
- Produto: O que é e para quem
- Base de usuários: Tamanho e tempo de uso
- Dados disponíveis: Quais métricas você tem acesso
Opcional:
- Resultados de Sean Ellis Survey (se já rodou)
- Curvas de retenção por cohort
- NPS score
- Unit economics (CAC, LTV)
- Taxa de crescimento orgânico
- Feedback qualitativo de usuários
Princípios fundamentais
1. PMF é óbvio quando existe
"Se você precisa perguntar se tem PMF, você não tem." — Eric Ries
Sinais claros de PMF:
- Demanda maior que capacidade de entrega
- Usuários reclamam quando produto fica fora do ar
- Crescimento orgânico forte (word of mouth)
- Clientes perguntam sobre pricing/timeline, não sobre features
- Time de vendas não consegue acompanhar inbound
2. PMF existe em segmentos
Você pode ter PMF forte com um segmento e zero com outro. Sempre segmente a análise.
3. PMF não é estático
PMF pode ser perdido por:
- Mudança de mercado
- Entrada de competitor superior
- Crescimento para segmentos sem fit
- Degradação de produto (tech debt, feature bloat)
4. PMF é multi-estágio
| Estágio | Descrição | Sean Ellis Score | Retenção |
|---|---|---|---|
| Nascent | Sinais iniciais, poucos usuários apaixonados | < 20% | Caindo |
| Developing | Segmento claro, mas ainda inconsistente | 20-39% | Estabilizando |
| Strong | Maioria dos usuários-alvo são retidos | 40-60% | Flat ou subindo |
| Extreme | Produto é indispensável, crescimento viral | > 60% | Smile curve |
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 · 301 lines · 0 tokens per session scan A fe27b2e37a30
measure-pmf 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 2,616 tokens. A static security scan graded it A with 0 findings. It is 100% identical to measure-pmf, 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.