triage-new-bugs

triage-new-bugs is a skill for Claude Code, Codex from openshift/ols. It costs 65 tokens per session (3,078 once invoked), scanned A, original, Apache-2.0.

A Jira bug-triage tool that reviews newly submitted bugs against the current project specifications. Bug triage means deciding whether a report needs a specification change, more information, or only implementation work.

In plain words
What is it for?
Use it to review all new bugs in the OLS Jira project or to analyze one specified bug. It also synchronizes workspace repositories and reports any repositories it could not update.
Why use it?
It helps separate specification problems from incomplete reports and ordinary coding fixes before anyone responds. It prepares comments for human approval instead of posting them automatically.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/openshift/ols/triage-new-bugs
Any agent
npx skills add openshift/ols --skill triage-new-bugs
Clone the repo
git clone --depth 1 https://github.com/openshift/ols

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for triage-new-bugs

README.md
[![agentmods](https://agentmods.dev/badge/skills/openshift/ols/triage-new-bugs.svg)](https://agentmods.dev/skills/openshift/ols/triage-new-bugs)
Your own site
<a href="https://agentmods.dev/skills/openshift/ols/triage-new-bugs"><img src="https://agentmods.dev/badge/skills/openshift/ols/triage-new-bugs.svg" alt="Measured on agentmods" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,078 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00065 $0.03078
Opus 5 $0.00032 $0.01539
Sonnet 5 $0.00013 $0.00616
Haiku 4.5 $0.00006 $0.00308

Measured yesterday against content hash 1bb6963ddffa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

triage-new-bugs 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 yesterday.

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.

.claude/skills/triage-new-bugs/SKILL.md · 319 lines

How it starts

The opening of the file, as written. The whole thing — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Triage New OLS Bugs

Fetch all New OLS Jira bugs, analyze each against the current .ai/spec/ files, classify each one, and present a report with draft Jira comments for human approval before posting anything.

Defaults

Setting Value
Project OLS
Cloud ID redhat.atlassian.net
Content format markdown
JQL project = OLS AND issuetype = Bug AND status = New

Single-Bug Test Mode

If an OLS-XXXX key is passed as an argument, skip the JQL fetch and analyze only that bug. The human approval gate still applies — do not post anything without explicit approval.

Step 1: Sync Repos

Pull all repos in the workspace to ensure the spec is at latest. Only attempt pull on directories that are git repos:

for repo in */; do
  if git -C "$repo" rev-parse --git-dir > /dev/null 2>&1; then
    result=$(git -C "$repo" pull --ff-only 2>&1)
    if [ $? -ne 0 ]; then
      echo "Warning: could not pull $repo — $result"
    else
      echo "OK: $repo"
    fi
  fi
done

Surface all warnings to the user. Continue even if some repos fail to pull, but note which repos may have stale spec content.

Step 2: Read the Spec Map

Do NOT read all spec files upfront — that would exceed usable context.

Instead, read only the spec index files to build a map of what each spec covers:

find . -path "*/.ai/spec/how/repo-map.md" -o \
       -path "*/.ai/spec/README.md" | sort

Read all discovered index files. This gives you a map of:

  • Which spec files exist per repo
  • What each spec file covers (from repo-map entries)
  • Which repos and components own which concerns

Hold this map in context. You will read individual spec files on demand in Step 5, not upfront. If you have already read a spec file within the last 5 bugs, you do not need to re-read it. Beyond that window, re-read the file — context compression may have evicted earlier content.

Step 3: Fetch New Bugs

Use searchJiraIssuesUsingJql:

cloudId: redhat.atlassian.net
jql: project = OLS AND issuetype = Bug AND status = New
fields: [summary, description, components, labels]
maxResults: 100

Read the full file on GitHub · 319 lines

Changes

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.

  1. yesterday Changed · +1 lines 1bb6963ddffa
  2. 5d ago First seen · 318 lines · 65 tokens per session scan A 887d85ba8f4c

Subscribe to this mod's changes

triage-new-bugs is a skill published in the GitHub repository openshift/ols (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 65 tokens to every session and 3,078 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens