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/ricneves-ai/flowgrammers-skillsWrote 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/ricneves-ai/flowgrammers-skills/user-story)<a href="https://agentmods.dev/commands/ricneves-ai/flowgrammers-skills/user-story"><img src="https://agentmods.dev/badge/commands/ricneves-ai/flowgrammers-skills/user-story/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/ricneves-ai/flowgrammers-skills/user-story"><img src="https://agentmods.dev/badge/commands/ricneves-ai/flowgrammers-skills/user-story.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.00031 | $0.00266 |
| Opus 5 | $0.00015 | $0.00133 |
| Sonnet 5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
user-story 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 9d 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
/user-story
Gera user stories estruturadas com critérios de aceite, story points e planejamento de capacidade de sprint.
Uso
/user-story generate Gera user stories (interativo)
/user-story sprint <capacidade> Planeja sprint com capacidade em story points
Formato de Entrada
O modo interativo solicita o contexto da feature. Para planejamento de sprint, informe a capacidade em story points:
/user-story generate
> Feature: Autenticação de usuário
> Persona: Gerente de engenharia
> Épico: Segurança da Plataforma
/user-story sprint 21
> Stories são classificadas por prioridade e cabem dentro de 21 pontos de capacidade
Exemplos
/user-story generate
/user-story sprint 34
/user-story sprint 21
Scripts
product-team/agile-product-owner/scripts/user_story_generator.py— Gerador de user story (args posicionais:sprint <capacidade>)
Referência de Skill
product-team/agile-product-owner/SKILL.md
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.
- 9d ago First seen · 44 lines · 0 tokens per session scan A d8212ea4c94c
user-story is a command published in the GitHub repository ricneves-ai/flowgrammers-skills (112 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 266 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.