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/prdgit 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/prd)<a href="https://agentmods.dev/commands/matheusbrramos/productflow/prd"><img src="https://agentmods.dev/badge/commands/matheusbrramos/productflow/prd.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.00006 | $0.00500 |
| Opus 5 | $0.00003 | $0.00250 |
| Sonnet 5 | $0.00001 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
prd 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 3d 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.
What it actually says
/prd - Criar Product Requirements Document
Cria PRD completo usando o agente Strategist.
Entrada
$ARGUMENTS
Se nenhum argumento for fornecido, perguntar o nome da feature ou produto.
Pre-requisitos
- Verificar se
.context/empresa.mdexiste - Recomendado: Discovery e pesquisa de mercado concluidos
Se pre-requisitos nao atendidos, orientar quais comandos rodar primeiro.
O que fazer
-
Entender o problema
- Analisar evidencias de discovery
- Verificar analise competitiva
- Questionar premissas
-
Criar PRD completo com todas as secoes:
- Sumario Executivo (problema, evidencias, solucao, outcome)
- Contexto (JTBD, personas, jornada)
- Requisitos Funcionais (detalhados, categorizados, priorizados)
- Requisitos Nao-Funcionais (performance, seguranca, compliance, etc)
- Escopo (in/out, premissas, restricoes)
- Epicos (alto nivel)
- Metricas de Sucesso
- Riscos
-
Marcar ambiguidades
- Usar [NEEDS CLARIFICATION] para questoes pendentes
- Listar premissas a validar
-
Garantir rastreabilidade
- Cada requisito linkado a evidencia
- Referencias a docs de discovery e research
REGRAS CRITICAS
- Definir O QUE e POR QUE, nunca o COMO
- Nao escrever codigo ou fazer decisoes tecnicas
- Nao incluir features especulativas
- Todos os requisitos devem ser testaveis
Output
Criar arquivo: docs/prd/{feature}.md
Usar estrutura completa do PRD com todas as secoes obrigatorias.
Proximos passos sugeridos
/pf-review- Revisar qualidade do PRD/stories <feature>- Detalhar user stories/pf-spec <feature>- Criar Software Design Document
Exemplos
/prd "Alertas inteligentes de vendas"
/prd "Sistema de autenticacao"
/prd "Modulo de relatorios"
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.
- 3d ago First seen · 76 lines · 6 tokens per session scan A 5fc40792db38
prd is a command published in the GitHub repository matheusbrramos/ProductFlow (2 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 500 once invoked, about $0.0000 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.