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/salesgit 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/sales)<a href="https://agentmods.dev/commands/matheusbrramos/productflow/sales"><img src="https://agentmods.dev/badge/commands/matheusbrramos/productflow/sales.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.00009 | $0.00556 |
| Opus 5 | $0.00005 | $0.00278 |
| Sonnet 5 | $0.00002 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
sales 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 5d 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
/sales - Materiais de Vendas
Aciona o agente Sales-Enabler para criar materiais comerciais.
Entrada
$ARGUMENTS
Se nenhum argumento for fornecido, apresentar catalogo e perguntar o que gerar.
Pre-requisitos
- PRD ou specs definidos
- Analise competitiva (recomendado)
- Insights de discovery (recomendado)
Catalogo de Materiais
APRESENTACOES a) Sales Deck (empresa/produto/feature) b) One-pager (problema->solucao->prova->CTA) c) Pitch deck para investidores
COMPETITIVO d) Battlecards por concorrente e) Matriz comparativa de mercado f) Playbooks taticos por concorrente
VENDAS g) Playbook por etapa do funil h) Talk tracks (roteiros por persona) i) Scripts de discovery j) Objection handling k) Guia de demo
COMUNICACAO l) Email templates m) WhatsApp templates n) Sequencias de nurturing
CASES E PROVAS o) Case brief p) ROI calculator
CAPACITACAO q) Onboarding 30-60-90 r) FAQs e glossario
O que fazer
-
Apresentar catalogo (se sem argumentos)
-
Perguntar:
- Quais materiais priorizar?
- Qual o objetivo?
- Publico-alvo? (SDR, AE, CSM)
- Mercado/persona foco?
-
Coletar insumos necessarios
- Buscar PRD e posicionamento
- Verificar analise competitiva
- Coletar quotes de discovery
-
Produzir material
- Usar estrutura padrao do tipo
- Marcar [PLACEHOLDER] quando faltar dados
- Versionar (v1.0)
REGRAS CRITICAS
- NUNCA inventar dados de produto, precos, prazos ou SLAs
- Sempre solicitar fonte ou marcar como [PLACEHOLDER]
- Versionar toda entrega
Output
Criar arquivos em docs/sales/ com estrutura especifica do tipo.
Exemplos
/sales
/sales gerar battlecard para Eventbrite
/sales gerar one-pager
/sales gerar playbook para etapa discovery
/sales gerar talk-track para Organizador Iniciante
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.
- 5d ago First seen · 94 lines · 9 tokens per session scan A 09410ce06c51
sales is a command published in the GitHub repository matheusbrramos/ProductFlow (2 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 556 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.