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 skills add openshift-eng/ai-helpers --skill create-release-notegit 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/skills/openshift-eng/ai-helpers/create-release-note)<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/create-release-note"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/create-release-note/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/openshift-eng/ai-helpers/create-release-note"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/create-release-note.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.00020 | $0.05693 |
| Opus 5 | $0.00010 | $0.02847 |
| Sonnet 5 | $0.00004 | $0.01139 |
| Haiku 4.5 | $0.00002 | $0.00569 |
Grade A, and why
create-release-note 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Create Release Note — 95% identical, 29 lines differ
How it starts
The opening of the file, as written. The whole thing — 796 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Release Note
This skill provides detailed step-by-step implementation guidance for the /jira:create-release-note command, which automatically generates bug fix release notes by analyzing Jira bug tickets and their linked GitHub pull requests.
When to Use This Skill
This skill is automatically invoked by the /jira:create-release-note command and should not be called directly by users.
Prerequisites
- MCP Jira server configured and accessible
- GitHub CLI (
gh) installed and authenticated - User has read access to the Jira bug
- User has write access to Release Note fields in Jira
- User has read access to linked GitHub repositories
Implementation Steps
Step 1: Fetch and Validate Jira Bug
Objective: Retrieve the bug ticket and validate it's appropriate for release note generation.
Actions:
-
Fetch the bug via
getJiraIssuewith the issue key andresponseContentFormat: "markdown". -
Parse the response:
- Extract
issuetype.name- verify it's "Bug" - Extract
description- full bug description text - Extract
issuelinks- array of linked issues - Extract
customfield_10785- current Release Note Type (if already set) - Extract
customfield_10783- current Release Note Text (if already set) - Extract
comment.comments- array of comment objects
- Extract
-
Validate issue type:
- If
issuetype.name != "Bug", show warning:Warning: {issue-key} is not a Bug (it's a {issuetype.name}). Release notes are typically for bugs. Continue anyway? (yes/no) - If user says no, exit without making changes
- If
-
Check if release note already exists:
- If
customfield_10783is not empty, show warning:This bug already has a release note: --- {existing release note} --- Do you want to regenerate it? (yes/no) - If user says no, exit without making changes
- If
Step 2: Parse Bug Description for Cause and Consequence
Objective: Extract the required Cause and Consequence sections from the bug description.
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 · 796 lines · 20 tokens per session scan A af76c1af88dc
create-release-note is a skill published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 5,693 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
review-change
Review a completed change against its authorizing spec in fresh context — evidence-based checks, severity-ranked findings, and a written verdict for the human's merge decision. Use when a diff needs reviewing before merge, or when add-feature / fix-bug / implement-spec reaches its review gate.
task
Create one or more tasks via wade task create — for a single bug/feature OR a full plan/PRD breakdown. This is the STANDALONE task-creation workflow, used whenever the user directly asks to create a task/issue outside a wade plan session. Assesses scope, proposes a single- or multi-issue breakdown with reasoning, gets…
RootCauseAnalysis
Structured incident investigation using Five Whys, Fishbone, blameless Postmortem, Fault Tree, Kepner-Tregoe, and FMEA — traces failures to systemic root causes rather than blaming humans. USE WHEN root cause, RCA, 5 whys, fishbone, postmortem, incident analysis, fault tree, why does this keep failing, blameless…
Vitals
Read-only macOS performance inspection: a deterministic CLI gathers the numbers, Interpretation.md turns them into a diagnosis instead of a data dump.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.