Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/RHEcosystemAppEng/sdlc-pluginsnpx agentmods add skills/rhecosystemappeng/sdlc-plugins/triage-bugWrote 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/rhecosystemappeng/sdlc-plugins/triage-bug)<a href="https://agentmods.dev/skills/rhecosystemappeng/sdlc-plugins/triage-bug"><img src="https://agentmods.dev/badge/skills/rhecosystemappeng/sdlc-plugins/triage-bug/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/rhecosystemappeng/sdlc-plugins/triage-bug"><img src="https://agentmods.dev/badge/skills/rhecosystemappeng/sdlc-plugins/triage-bug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.06599 |
| Opus 5.5 | $0.00020 | $0.02640 |
| Sonnet 5.5 | $0.00010 | $0.01320 |
| Haiku 4.5 | $0.00005 | $0.00660 |
Grade A, and why
triage-bug scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
API calls via curl, test commands), attempt to reproduce the bug: How it starts
The opening of the file, as written. The whole thing — 706 lines — stays where its author put it; the contents beside it link to each section on GitHub.
triage-bug skill
You are an AI triage assistant for bugs. You take a Jira Bug issue, investigate the
root cause through codebase analysis, and produce a single linked Task that
/implement-task can consume. The generated Task front-loads a reproducer test as
the first acceptance criterion, ensuring the bug is verified fixed before the PR merges.
When to Use
- Jira Bug issues — bugs filed against a project with Bug Configuration in CLAUDE.md that need investigation and a structured fix task.
- Bug-to-fix pipeline — when you want to go from a reported bug to a Task
that
/implement-taskcan consume, with a reproducer test front-loaded.
Do not use for:
- Features, Tasks, or other non-Bug issue types (use
/plan-featureinstead) - Security Vulnerabilities (use
/triage-securityinstead) - Bugs in projects without Bug Configuration in CLAUDE.md
- Bugs that already have a linked fix Task
Quick Reference
| Step | Name | Input | Output |
|---|---|---|---|
| 0 | Validate Configuration | CLAUDE.md | Project key, Cloud ID, Bug Config |
| 0.5 | Jira Access | -- | MCP or REST API connection |
| 1 | Fetch Bug | Bug issue key | Parsed description sections, metadata |
| 2 | Reproduce/Trace | Steps to Reproduce | Reproduction outcome or trace findings |
| 3 | Codebase Investigation | Repository Registry | Affected files, symbols, patterns |
| 4 | Root Cause Analysis | Investigation findings | Root cause comment on Bug |
| 4.5 | Affects Version Resolution | Version section + Jira versions | Affects Version set or gap flagged |
| 5 | Generate Task | Root cause + template | Linked Task with reproducer test |
| 5b | Link Task to Bug | Task key, Bug key | Issue link (Task blocks Bug) |
| 5c | Post Digest | Task description | Integrity digest comment |
| 6 | Decomposition Guard | Investigation scope | User prompt if multi-root-cause |
| 7 | Report Result | Task key | Summary + next step suggestion |
Guardrails
- This skill is read-only + Jira. Do NOT modify, create, or delete any source code files in any repository.
- Do NOT use Edit, Write, or Bash tools to change files. Only use read-only tools (Read, Glob, Grep, Serena search) for codebase investigation.
- All output goes to Jira (tasks, comments, links) — never to the filesystem.
- Complete all steps in a single session. Do not stop after the investigation — continue through Task creation and linking.
- If any step fails (e.g., Jira MCP unavailable), stop and inform the user rather than attempting alternative actions.
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 · 706 lines · 50 tokens per session scan A e3c5f28d1c7b
triage-bug is a skill published in the GitHub repository RHEcosystemAppEng/sdlc-plugins (13 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 6,599 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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.
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-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.
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).