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 wangke19/gemini-ai-helpers --skill create-release-notegit clone --depth 1 https://github.com/wangke19/gemini-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/wangke19/gemini-ai-helpers/create-release-note)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/create-release-note"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-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/wangke19/gemini-ai-helpers/create-release-note"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/create-release-note.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.00020 | $0.05724 |
| Opus 5.5 | $0.00008 | $0.02290 |
| Sonnet 5.5 | $0.00004 | $0.01145 |
| Haiku 4.5 | $0.00002 | $0.00572 |
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 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.
This is a copy
95% identical to create-release-note — 29 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 809 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 using MCP:
mcp__atlassian__jira_get_issue( issue_key=<issue-key>, fields="summary,description,issuetype,status,issuelinks,customfield_10785,customfield_10783,comment" ) -
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 gracefully
- 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 gracefully
- If
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 · 809 lines · 20 tokens per session scan A fa37fdd6a40c
Create Release Note is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 5,724 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to create-release-note, differing in 29 lines, and is treated as a copy.
Other skills, from other repositories
gh-cli
GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
jira-release
Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.
prepare
Draft release-preparation artefacts for : the planning issue, the version-bump and changelog prep PR (with the first-release review of what the source archive ships), the post-release dev-version bump PR, and, for ASF projects, the one-time automated-signing setup. Every output is a draft the RM confirms; nothing is…
archive-sweep
Scan the release distribution area (dist/release/ / when releasedistbackend = svnpubsub, or the configured distribution location), identify releases past the project's retention rule, and propose the backend-shaped command set to move them to the archive area. Read-only on the distribution surface; the RM executes…