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/github/issue.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/issue)<a href="https://agentmods.dev/commands/watt-mind/coach/issue"><img src="https://agentmods.dev/badge/commands/watt-mind/coach/issue/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/watt-mind/coach/issue"><img src="https://agentmods.dev/badge/commands/watt-mind/coach/issue.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.00000 | $0.00503 |
| Opus 5.5 | $0.00000 | $0.00201 |
| Sonnet 5.5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
issue 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 2mo 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 = "Create and process GitHub issues according to project rules." prompt = """ Your goal is to assist the user in managing GitHub issues for the repository, strictly adhering to the project's issue management guidelines.
User input: {{args}}
1. Preparation
- Read Guidelines: First, read
docs/04-guides/issue-management.mdto load the current templates, labeling strategy, and best practices. - Context: You are working in the
newpush/coachrepository.
2. Modes of Operation
Mode A: Create Issue
If the user wants to create a bug, feature request, or maintenance task:
- Search: First, run
gh issue list --search "<keywords>"to check for existing duplicates. - Gather Info: If the user hasn't provided enough info, ask for:
- Type (Bug, Feature, Maintenance)
- Description/Summary
- Steps to Reproduce (for bugs) or Use Case (for features)
- Draft: Create the issue body using the exact markdown template from the documentation.
- Title: Keep it clean and descriptive. Do NOT use prefixes like
[Component]. - Labels: Select appropriate labels from the standard list (e.g.,
bug,enhancement,ui/ux,backend,data,planning,wellness).
- Title: Keep it clean and descriptive. Do NOT use prefixes like
- Confirm: Present the Title, Labels, and Body summary to the user for approval.
- Execute: Run
gh issue create --title "..." --body "..." --label "...".
Mode B: Triage / Process
If the user wants to review or clean up issues:
- List: Run
gh issue list(optionally with filters). - Analyze: Check for:
- Titles: Are they clean? (Remove
[Prefixes]). - Labels: Are they standard? (Remove
Type: Bug,Area: ...if found).
- Titles: Are they clean? (Remove
- Fix: Use
gh issue edit <number>to rename titles or update labels.
3. Execution
- If
{{args}}is empty, ask the user what they want to do (Create or Triage). - If
{{args}}contains a description (e.g., "login is broken"), proceed to Mode A. """
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.
- 2mo ago First seen · 38 lines · 0 tokens per session scan A dd7b86b81f5c
issue is a command published in the GitHub repository watt-mind/coach (105 stars, last pushed 14d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 503 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.
issue compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| issuewatt-mind/coach | Command | 105 | 14d ago | Apache-2.0 | A | 0 | Gemini CLI |
| triagen8n-io/n8n | Command | 210k | yesterday | none | A | 7 | Claude Code |
| sync-usagetechysy/10router | Command | 98 | today | MIT | A | 140 | Claude Code |
| cardustoppble/overclick | Command | 119 | 2d ago | MIT | A | 8 | Claude Code |
| checkjmagar/claude-homelab | Command | 87 | 1mo ago | MIT | A | 10 | Claude Code |
| /opsx-applycoeusyk/inference-x | Command | 2 | 1mo ago | MIT | A | 16 | Claude Code, Cursor |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |