Borrowing it
Nothing to install: this file belongs to warpdotdev/oz-skills. 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/warpdotdev/oz-skills/main/.agents/skills/github-bug-report-triage/SKILL.mdgit clone --depth 1 https://github.com/warpdotdev/oz-skillsWrote 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/warpdotdev/oz-skills/github-bug-report-triage)<a href="https://agentmods.dev/skills/warpdotdev/oz-skills/github-bug-report-triage"><img src="https://agentmods.dev/badge/skills/warpdotdev/oz-skills/github-bug-report-triage/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/skills/warpdotdev/oz-skills/github-bug-report-triage"><img src="https://agentmods.dev/badge/skills/warpdotdev/oz-skills/github-bug-report-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
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.00036 | $0.01032 |
| Opus 5.5 | $0.00014 | $0.00413 |
| Sonnet 5.5 | $0.00007 | $0.00206 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
github-bug-report-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 1mo 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Bug Report Triage
Evaluate GitHub issues for bug reports only. Determine if they contain sufficient info to be actionable. If not, identify missing details and provide constructive feedback.
Workflow
1. Locate Issue Template
Check for existing templates:
.github/ISSUE_TEMPLATE/bug_report.md.github/ISSUE_TEMPLATE/bug_report.yml.github/ISSUE_TEMPLATE/*.md.github/ISSUE_TEMPLATE.mdISSUE_TEMPLATE.md
If no template exists, use references/ISSUE_TEMPLATE.md from this skill as the fallback template, then evaluate the issue against it.
2. Evaluate Issue Quality
Critical questions:
-
Is this a bug report?
- If the issue is a feature request or a question, do not evaluate this issue
-
Is the description clear?
- What's broken or wrong
- Expected behavior vs. what actually happens
- Impact or severity
-
Can we reproduce it?
- Step-by-step reproduction
- OR sandbox/StackBlitz/CodeSandbox link
- OR minimal code example
Be reasonable:
- Don't require every template field to be filled
- Focus on minimum info needed to investigate
- Consider context (obvious bugs vs. edge cases)
3. Make Determination
Ready to be actionable:
- Has clear problem description
- Includes reproduction path OR enough context to debug
- Actually a bug (not feature/question)
Needs more info:
- Vague description ("it doesn't work")
- Missing reproduction steps AND no code example
- Unclear what the expected behavior should be
- Missing critical context (e.g., "crashes" but no error message)
4. Provide Feedback
If ready: Confirm issue is actionable.
If needs info: Specify what's missing. Be constructive and specific.
Examples
Example 1: Ready to Investigate
**Issue**: Dropdown menu doesn't close on mobile Safari
**Description**:
When clicking a dropdown menu item on iOS Safari, the menu stays
open instead of closing. Works fine on desktop Chrome/Firefox.
**Steps**:
1. Visit https://stackblitz.com/edit/my-repro
2. Open on iOS Safari
3. Click dropdown, select any item
4. Menu stays open (should close)
**Environment**: iOS 16.3, Safari
What ships with it
1 file 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.
- 1mo ago First seen · 162 lines · 36 tokens per session scan A e4289faf56f8
github-bug-report-triage is a skill published in the GitHub repository warpdotdev/oz-skills (822 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 1,032 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
bug-triage
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.
triage-issue-reports
Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
moai-lane-watchdog
One lane stall watchdog iteration: measure lane progress on three channels, classify the stall cause, apply the remedy or resolve the judgment through the decision ladder — instead of waiting on a reply — then record the outcome and report. Reads the unified --auto doctrine at…
investigation
Create an investigation ticket + live-doc for sustained root-cause work (retros, bug archaeology, regression hunts).