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.
npx agentmods add skills/watt-mind/coach/report-bugnpx skills add watt-mind/coach --skill report-buggit 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/skills/watt-mind/coach/report-bug)<a href="https://agentmods.dev/skills/watt-mind/coach/report-bug"><img src="https://agentmods.dev/badge/skills/watt-mind/coach/report-bug.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 | $0.00053 | $0.02058 |
| Opus 5 | $0.00026 | $0.01029 |
| Sonnet 5 | $0.00011 | $0.00412 |
| Haiku 4.5 | $0.00005 | $0.00206 |
Grade A, and why
report-bug 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.
How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Bug Skill
Automatically generate comprehensive, professional bug reports and post them directly to the GitHub repository associated with the current working directory.
Purpose
This skill automates the creation of detailed bug reports that include:
- Clear, concise issue titles
- Step-by-step reproduction instructions
- Technical analysis and root cause insights
- Recommended E2E test specifications
- Professional formatting suitable for team collaboration
When to Use This Skill
Use this skill when:
- Documenting a bug discovered during development or testing
- Creating a GitHub Issue to track a problem
- Generating a professional bug report with reproduction steps
- Providing E2E test recommendations for verification
- Ensuring consistent bug reporting standards across the team
Workflow
1. Repository Detection
Detect the Git repository in the current working directory:
- Extract the repository owner and name from the remote origin URL
- Validate that the repository is a GitHub repository
- Handle both HTTPS and SSH remote URL formats
2. Bug Report Generation
Create a comprehensive bug report following this structure:
Issue Title: Clear, concise summary (max 80 characters)
Issue Body:
## Summary
[Clear description of the issue including what went wrong and expected behavior]
## Reproduction Steps
1. [First step to reproduce]
2. [Second step to reproduce]
3. [Third step to reproduce]
...
## Environment
- **OS**: [Operating system and version]
- **Browser/Runtime**: [Browser or Node.js version]
- **Version**: [Application or package version]
## Technical Details
- **Component**: [Affected component/module/file]
- **Severity**: [Critical/High/Medium/Low]
- **Affected Users**: [Scope of impact]
## Findings and Insights
### Root Cause Analysis
[Detailed technical analysis from the debugging session, explaining why the bug occurs]
### Code Locations
[Specific files, functions, and line numbers where the issue manifests]
### Potential Impact
[Description of how this bug affects users and system behavior]
### Dependencies Affected
[Other components or systems that may be impacted]
## Recommended E2E Test
```typescript
describe('Bug Fix Verification', () => {
it('should [expected behavior after fix]', async () => {
// Arrange: Set up test conditions
// Act: Execute the action that previously triggered the bug
// Assert: Verify the bug is fixed
})
})
```
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 330 lines · 53 tokens per session scan A 7033e6541cd1
report-bug is a skill published in the GitHub repository watt-mind/coach (83 stars, last pushed 3d ago), licensed Apache-2.0. It adds 53 tokens to every session and 2,058 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
hypertrophy-training
Evidence-based muscle hypertrophy training, nutrition, exercise selection, periodization, recovery, supplements, and progress tracking. Use when Codex needs to build strength-training programs, set volume or RIR targets, choose exercises, troubleshoot plateaus, calculate macros/TDEE, or answer bodybuilding and…
cycling-training
Cycling training plans, power zones, FTP testing, intervals, periodization, indoor/outdoor training, race preparation, training-load analysis, and recovery guidance. Use when Codex needs to design cycling workouts, calculate FTP-based zones or TSS, analyze training data, manage CTL/ATL/TSB, or answer cyclist training…
intervals-icu
Intervals.icu API workflows for fetching and updating wellness, activities, fitness metrics, events, zones, power curves, activity streams, and uploads. Use when Codex needs to call Intervals.icu, prepare authenticated API commands, export athlete data, debug API responses, or pair platform data with cycling-training…
process-automation-audit
Scope, sell, run, and package paid audits for manual business process automation. Use when Codex needs to help with discovery, scoping, pricing, stakeholder questions, process maps, audit deliverables, pilot proposals, or negotiation boundaries for automating operational workflows such as invoices, price lists…
strava
Query Strava fitness data including activities, athlete stats, segments, routes, clubs, and gear. Use when the user asks about cycling, running, swimming, workouts, training, or Strava data.
garmin-connect
Query Garmin Connect fitness and health data including activities, athlete stats, sleep, heart rate, stress, and body battery. Use when the user asks about Garmin data, workouts, training, or health metrics.