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.
git clone --depth 1 https://github.com/openshift-eng/ai-helpersWrote 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/openshift-eng/ai-helpers/validate-bug)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/validate-bug"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/validate-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/commands/openshift-eng/ai-helpers/validate-bug"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/validate-bug.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.00025 | $0.01141 |
| Opus 5.5 | $0.00010 | $0.00456 |
| Sonnet 5.5 | $0.00005 | $0.00228 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
validate-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 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
jira:validate-bug
Synopsis
/jira:validate-bug <PR-URL | PR-number | JIRA-key> [--branch release-4.X|main|master]
Description
The jira:validate-bug command diagnoses why the Prow jira/invalid-bug label was applied to a PR. It runs the same 7 validation checks as the jira-lifecycle-plugin, reports pass/fail for each check, and offers to fix failing checks via JIRA MCP tools.
This command is essential for:
- Diagnosing why a PR is stuck with
jira/invalid-bug - Understanding which JIRA fields need correction
- Fixing JIRA bugs in-place without manual field hunting
- Batch-diagnosing multiple blocked PRs
Key Features
- 7-Check Validation — Same checks as the Prow plugin: open state, target version, valid status, release notes, dependent bug states, dependent target versions, dependents exist
- PR-Aware — Accepts PR URLs/numbers, auto-extracts JIRA key from title and branch context
- Fix Mode — After diagnosis, offers to fix failing checks via JIRA MCP tools
- Branch-Aware — Computes expected target version and dependent version from the PR's base branch
Implementation
For detailed implementation guidance, see the validate-bug skill.
High-Level Workflow
- Resolve Input — Parse PR URL/number or JIRA key. Extract JIRA key from PR title and target branch via
gh pr view. - Gather Data — Fetch the JIRA bug with all fields via MCP. Follow issue links to find dependent bugs.
- Validate — Run all 7 checks against the branch-specific expected values. Produce a pass/fail results table.
- Report — Render results matching the jira-lifecycle-plugin bot comment format, with fix instructions for each failure.
- Offer Fixes — List fixable failures, ask for confirmation, then apply fixes via MCP tools.
Usage Examples
From PR URL
/jira:validate-bug https://github.com/openshift/hypershift/pull/8811
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 · 107 lines · 25 tokens per session scan A 3c0951a3e089
validate-bug is a command published in the GitHub repository openshift-eng/ai-helpers (121 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 1,141 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-09-05.
Other commands, from other repositories
bug-report
Draft a bug report issue for lean4-skills.
speckit.companion.doctor
Report on a spec's run health — unfinished steps, unjournaled tasks, step bleed, drift you can judge, a step that closed having verified nothing, a step that closed without the file it promised, and why completion did not land (read-only, retroactive, never halts).
postmortem
Deliver a structured post-mortem after incidents, mistakes, or stuck sessions. Use when the user requests a structured post-mortem after incidents, mistakes, or stuck sessions.
audit
Audit closed tickets for regressions against today's code (unchanged, evolved, implemented wrong, not implemented), plus duplicate and groupable open ones.
harness:maintenance-pipeline
On-demand, report-first maintenance sweep — runs overdue checks via harness maintenance run, triages findings, and asks the human in plain text before dispatching any fix.
forense
Investigação post-mortem de workflows framework com falha — analisa histórico git, artefatos e estado para diagnosticar o que deu errado.