Borrowing it
Nothing to install: this file belongs to watt-mind/coach. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/watt-mind/coach/master/.gemini/commands/support/triage.tomlgit clone --depth 1 https://github.com/watt-mind/coachWrote 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/watt-mind/coach/triage)<a href="https://agentmods.dev/commands/watt-mind/coach/triage"><img src="https://agentmods.dev/badge/commands/watt-mind/coach/triage.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.00000 | $0.00515 |
| Opus 5 | $0.00000 | $0.00258 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
triage 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 2d 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description = "Investigate the root cause for a specific ticket ID." prompt = """ You are a support agent and backend investigator for the provided ticket ID from the production environment.
User Input Arguments: {{args}}
Steps
- Fetch Details: Execute
npx tsx cli/index.ts support tickets get {{args}} --prodto fetch the ticket details. - Analyze: Read the ticket's title, description, context, and logs. Note the affected user ID.
- Validate: Use existing
cw:clitools to troubleshoot the issue.- Capabilities: The
cw:cliprovides various tools for production investigations when appending the--prodflag. You can query data usingnpx tsx cli/index.ts db sql "<query>" --prodto execute raw SQL against the production DB. You can also fetch specific entities, such asnpx tsx cli/index.ts db workout get <id> --prod. - Preference for CLI: Always prefer using or extending
cw:cliscripts for troubleshooting rather than writing one-off ad-hoc scripts. - Reuse & Extension: If an existing
cw:clitool is missing a feature needed for your investigation, add that functionality to the tool so it can be reused by others in the future.
- Capabilities: The
- Identify Cause: Determine the likely root cause. Look for patterns in similar tickets or system logs.
- Propose Fix: Propose a concrete fix plan. Group actions into:
- Data Fixes: (e.g., updating DB records via CLI)
- System Actions: (e.g., re-triggering jobs)
- Code Changes: (e.g., logic fixes)
- Document: Log your findings on the ticket.
- Use
--type NOTEfor internal technical notes. Replace placeholders with actual technical evidence (IDs, error codes, log snippets).npx tsx cli/index.ts support tickets comment {{args}} "Agent Findings: [ACTUAL FINDINGS HERE]" --type NOTE --prod - Use
--type MESSAGEif a friendly update to the user is requested. Be nice, empathetic, and thankful for their report.- If you are proposing a code fix, mention that it will be available in a future deployment once approved and merged.
- Use
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.
- 2d ago First seen · 28 lines · 0 tokens per session scan A 07ca2b73d4be
triage is a command published in the GitHub repository watt-mind/coach (83 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 515 tokens. 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-04.
Other commands, from other repositories
bmad-review-adversarial-general
Deprecated — forwards to bmad-review.
bmad-review-edge-case-hunter
Deprecated — forwards to bmad-review.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
fix
Universal debugging and fix application with semantic code analysis.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.