Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add pwdev-solucoes/pwdev-claude-marketplace/plugin install pwdev-glpiWrote 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/pwdev-solucoes/pwdev-claude-marketplace/triagem)<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/triagem"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/triagem/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/pwdev-solucoes/pwdev-claude-marketplace/triagem"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/triagem.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.00017 | $0.00478 |
| Opus 5 | $0.00009 | $0.00239 |
| Sonnet 5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
triagem 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 6d 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
/pwdev-glpi:triagem
STEP 0 — Idioma
${CLAUDE_PLUGIN_ROOT}/references/language.md
Gate
search_tickets {"limit": 1} falhou → apontar /pwdev-glpi:init (ou
reinício de sessão, se check-setup.sh estiver verde) e parar.
STEP 1 — Fila
Escopo default: {"status": ["new"], "sort": "date_creation", "order": "ASC", "limit": 20} (mais antigo primeiro). Refinos de $ARGUMENTS mapeados para o
schema do search_tickets (grupo → assignee_group_id/requester_group_id,
"urgência 4+" → urgency, período → date_creation_from/to). Filtros exatos:
${CLAUDE_PLUGIN_ROOT}/references/mcp-tools.md.
Apresente a fila em tabela: id, título, requester, urgency/impact, idade (dias desde a criação).
STEP 2 — Triagem por chamado
Pergunte quais tickets triar (um, alguns ou os N primeiros). Para cada um:
- Invocar o prompt MCP
triage_ticket {ticket_id}e seguir suas instruções (categoria incidente/requisição, prioridade 1–5 justificada, 3 próximas ações, indícios de duplicata). - Traduzir o resultado em ações executáveis propostas:
update_ticket(urgency, impact,itilcategories_id, assignee) e/ouadd_ticket_followup(pergunta ao requester, nota de triagem).
STEP 3 — Execução
Mostrar a tabela de propostas (ticket → ação → parâmetros) e executar somente as confirmadas, uma a uma, reportando cada resultado.
Regras: nunca fechar chamado em triagem (fechamento exige solução — fluxo
próprio da skill glpi); nunca setar priority (propor urgency×impact).
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.
- 6d ago First seen · 40 lines · 17 tokens per session scan A 7268c7cf1ee1
triagem is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 17 tokens to every session and 478 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
standup
Quick daily standup from today's Claude Code sessions — grouped by project, with cost and errors.
fire-todos
Capture, list, and manage todos during work sessions.
gsd:resume-work
Resume work from previous session with full context restoration.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
ops
Weekly operations loop — triage the inquiry inbox, advance the CRM pipeline, sweep open PRs across repos, and surface the content plan. Loads the ops skill.
standup
A command that creates a daily stand-up report by summarizing recent work, planned tasks, calendar events, and blockers.