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/luanpdd/kit-mcpWrote 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/luanpdd/kit-mcp/fluxos-trabalho)<a href="https://agentmods.dev/commands/luanpdd/kit-mcp/fluxos-trabalho"><img src="https://agentmods.dev/badge/commands/luanpdd/kit-mcp/fluxos-trabalho.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.00029 | $0.00544 |
| Opus 5 | $0.00015 | $0.00272 |
| Sonnet 5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
fluxos-trabalho 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.
What it actually says
/fluxos-trabalho
Gerencia fluxos de trabalho paralelos para trabalho concurrent em milestones.
Uso
/fluxos-trabalho [subcomando] [argumentos]
Subcomandos
| Comando | Descrição |
|---|---|
list |
Listar todos os fluxos com status |
create <nome> |
Criar um novo fluxo de trabalho |
status <nome> |
Status detalhado de um fluxo |
switch <nome> |
Definir fluxo ativo |
progress |
Resumo de progresso de todos os fluxos |
complete <nome> |
Arquivar um fluxo concluído |
resume <nome> |
Retomar trabalho em um fluxo |
Passo 1: Analisar Subcomando
Analisar a entrada do usuário para determinar qual operação de fluxo executar.
Se nenhum subcomando for fornecido, padrão é list.
Passo 2: Executar Operação
list
Executar: node "$TOOLS" workstream list --raw --cwd "$CWD"
Exibir os fluxos em formato de tabela mostrando nome, status, fase atual e progresso.
create
Executar: node "$TOOLS" workstream create <nome> --raw --cwd "$CWD"
Após criação, exibir o caminho do novo fluxo e sugerir próximos passos:
/novo-marco --ws <nome>para configurar o milestone
status
Executar: node "$TOOLS" workstream status <nome> --raw --cwd "$CWD"
Exibir detalhamento de fases e informações de estado.
switch
Executar: node "$TOOLS" workstream set <nome> --raw --cwd "$CWD"
Também definir variável de ambiente WORKSTREAM para a sessão atual.
progress
Executar: node "$TOOLS" workstream progress --raw --cwd "$CWD"
Exibir visão geral de progresso de todos os fluxos.
complete
Executar: node "$TOOLS" workstream complete <nome> --raw --cwd "$CWD"
Arquivar o fluxo em milestones/.
resume
Definir o fluxo como ativo e sugerir /retomar-trabalho --ws <nome>.
Passo 3: Exibir Resultados
Formatar a saída JSON do tools em exibição legível por humanos.
Incluir a flag ${WS} em qualquer sugestão de roteamento.
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 · 65 lines · 29 tokens per session scan A 29383c308876
fluxos-trabalho is a command published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 544 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-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.