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/resolve.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/resolve)<a href="https://agentmods.dev/commands/watt-mind/coach/resolve"><img src="https://agentmods.dev/badge/commands/watt-mind/coach/resolve.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.00464 |
| Opus 5 | $0.00000 | $0.00232 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
resolve 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.
What it actually says
description = "Apply the approved fix and resolve a specific ticket ID." prompt = """ You are resolving a ticket after a fix plan has been approved.
User Input Arguments: {{args}}
Steps
- Context Check: Ensure you understand the approved fix actions. Run
npx tsx cli/index.ts support tickets get {{args}} --prodto refresh context if needed. - Apply Fix: Execute the approved actions (CLI commands, job triggers, or code edits).
- Preference for CLI: Use
cw:clicommands for data/sync fixes.
- Preference for CLI: Use
- Resolve: Update the ticket status to
RESOLVED:npx tsx cli/index.ts support tickets update-status {{args}} RESOLVED --prod - Document:
- Use a
NOTEto document the exact technical resolution (e.g., "Updated workout status via CLI").npx tsx cli/index.ts support tickets comment {{args}} "Fix applied: [TECHNICAL DETAILS]" --type NOTE --prod - Use a
MESSAGEto notify the user. Be exceptionally nice, thankful for their patience, and professional.- CRITICAL: If the fix involved a Code Change, you MUST state that the fix will be live with the next deployment (it is not immediate).
- Example (Data Fix):
npx tsx cli/index.ts support tickets comment {{args}} "Hi! Thank you so much for your patience. I've manually corrected the issue with your [ISSUE AREA] in the database. You should see it correctly now. Let us know if you need anything else!" --type MESSAGE --prod - Example (Code Fix):
npx tsx cli/index.ts support tickets comment {{args}} "Hi! We've identified the bug and implemented a fix in the codebase. Thank you for reporting this! The fix will be included in our next deployment (usually within 24-48 hours). We appreciate your help in making the app better!" --type MESSAGE --prod
- Use a
- Report: Confirm completion to the developer.
References
- Refer to
docs/04-guides/support.mdfor standard support procedures. """
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 · 25 lines · 0 tokens per session scan A 7b8e4786927a
resolve 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 464 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
start-development
Start development workflow process in Moira.
deliver
Verify, push, measure, and deliver the current OverClick card.
claim
Claim an OverClick card and load its execution briefing.
board
Show the actionable OverClick queue and this token's active claims.
card
Open one self-contained OverClick card.
bmad-sprint-planning
Check that planning is complete enough to implement, then generate the sprint status file from the epics. Can also summarize sprint progress and validate or repair the tracking file. Use when the user says "run sprint planning", "generate sprint plan", "check implementation readiness", "show sprint status", "validate…