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/storiesgit 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/stories)<a href="https://agentmods.dev/commands/matheusbrramos/productflow/stories"><img src="https://agentmods.dev/badge/commands/matheusbrramos/productflow/stories.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.00009 | $0.00624 |
| Opus 5 | $0.00005 | $0.00312 |
| Sonnet 5 | $0.00002 | $0.00125 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
stories 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/stories - Criar User Stories Detalhadas
Cria user stories detalhadas usando o agente Story-Writer.
Entrada
$ARGUMENTS
Se nenhum argumento for fornecido, perguntar qual feature ou PRD detalhar.
Pre-requisitos
- PRD aprovado (criado por /prd)
.context/empresa.mddeve existir
Se PRD nao existir, orientar a rodar /prd primeiro.
Selecao de Modelo
SEMPRE perguntar ao PM antes de comecar:
Qual modelo voce deseja usar para esta sessao de escrita de stories?
1. **Modelo completo** (Sonnet/Opus) - Para stories complexas com muitos edge cases
2. **Modelo economico** (Haiku) - Para stories simples e bem definidas
3. **Deixar eu decidir** - Vou sugerir baseado na complexidade da tarefa
Aguardo sua escolha antes de prosseguir.
O que fazer
-
Analisar PRD ou feature
- Identificar requisitos funcionais
- Entender personas e JTBD
- Mapear epicos
-
Quebrar em user stories
- Formato: Como [persona] Quero [acao] Para [beneficio]
- Garantir independencia (INVEST)
- Manter rastreabilidade aos requisitos
-
Escrever acceptance criteria
- Formato Gherkin (Given/When/Then)
- Cobrir cenario principal (happy path)
- Cobrir excecoes e edge cases
-
Adicionar metadata
- Prioridade (P0/P1/P2/P3)
- Estimativa (XS/S/M/L/XL)
- Dependencias entre stories
- Definition of Done
Output
Criar arquivo: docs/stories/{feature}.md
Estrutura do Output
# User Stories - [Feature]
**PRD:** [referencia]
**Data:** YYYY-MM-DD
**Modelo usado:** [completo/economico]
## Story Map
[Visualizacao opcional]
## Stories
### US-001: [Titulo]
**Epic:** [nome]
**Requisitos:** [RF-XXX]
**Como** [persona]
**Quero** [acao]
**Para** [beneficio]
#### Acceptance Criteria
```gherkin
Scenario: [descricao]
Given [contexto]
When [acao]
Then [resultado]
Prioridade: P0 Estimativa: M Dependencias: -
## Proximos passos sugeridos
- `/pf-review` - Revisar qualidade das stories
- Entregar para time de desenvolvimento
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 · 112 lines · 9 tokens per session scan A eebc97da1765
stories 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 624 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.
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.