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 agentmods add commands/matheusbrramos/productflow/discoverygit clone --depth 1 https://github.com/matheusbrramos/ProductFlowWrote 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/matheusbrramos/productflow/discovery)<a href="https://agentmods.dev/commands/matheusbrramos/productflow/discovery"><img src="https://agentmods.dev/badge/commands/matheusbrramos/productflow/discovery.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 | $0.00011 | $0.00657 |
| Opus 5 | $0.00005 | $0.00329 |
| Sonnet 5 | $0.00002 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
discovery 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 4d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/discovery - Analise de Usuarios
Realiza pesquisa qualitativa de usuarios usando o agente Discovery.
Entrada
$ARGUMENTS
Se nenhum argumento for fornecido, perguntar:
- Qual acao deseja? (analyze, interview, ost, jtbd, synthesize)
- Quais dados ou contexto fornecer?
Pre-requisitos
Verificar se .context/empresa.md existe. Se nao existir, orientar a rodar /setup primeiro.
Acoes Disponiveis
analyze
Analisa transcricoes de entrevistas, surveys ou dados qualitativos.
O que fazer:
- Processar dados fornecidos
- Extrair quotes relevantes
- Identificar padroes (critico, importante, relevante)
- Mapear Jobs-to-be-Done
- Sugerir oportunidades
interview
Prepara guia de entrevista para um perfil especifico.
O que fazer:
- Definir objetivo da entrevista
- Criar estrutura (abertura, contexto, experiencia, momento critico)
- Incluir dicas de conducao
- Gerar perguntas no formato correto (comportamento, nao hipotetico)
ost
Cria ou atualiza Opportunity Solution Tree.
O que fazer:
- Definir outcome de negocio
- Mapear oportunidades dos usuarios
- Listar solucoes por oportunidade
- Sugerir experimentos de validacao
jtbd
Mapeia Jobs-to-be-Done de um segmento.
O que fazer:
- Identificar job principal
- Mapear jobs secundarios
- Usar formato: QUANDO [situacao] QUERO [motivacao] PARA QUE [resultado]
synthesize
Consolida todos os insights de discovery em um documento.
Output
Criar arquivo com formato: docs/discovery/{tema}-YYYY-MM-DD.md
Estrutura do Output
# Analise de Discovery - [Tema]
**Data:** YYYY-MM-DD
**Entrevistas:** N
**Perfil:** [descricao]
## Jobs-to-be-Done
### Job Principal
### Jobs Relacionados
## Padroes Identificados
### Critico (N/N mencionaram)
### Importante (N/N mencionaram)
### Relevante (N/N mencionaram)
## Oportunidades
## Recomendacoes
## Anexo: Quotes
Proximos passos sugeridos
/prd <feature>- Criar especificacao/research- Complementar com pesquisa de mercado
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.
- 4d ago First seen · 106 lines · 11 tokens per session scan A 944fbe148fb3
discovery is a command published in the GitHub repository matheusbrramos/ProductFlow (2 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 657 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.